VALIDATION_ERROR | 400 | Request body or query failed schema validation. message names every failing field. See Validation errors. |
BAD_REQUEST | 400 | Generic client-input failure covering several situations: an illegal status transition (e.g. nothing leaves CANCELLED; the message names the booking’s current status), a mismatched currency between an order and an item you’re adding to it, cancelling an AWAITING_CONFIRMATION booking with your key, a payment intent for an order that owes nothing, an unparseable pagination cursor (except on the supplier’s alerts list, which answers INVALID_CURSOR), and other malformed input. message names the specific problem. |
HTTP_ERROR | 400, 401 | A request refused before its route ran. 401 on an end-user route: a missing or malformed Authorization header, or a user token that is invalid or expired — sign in again. 400: a body that isn’t valid JSON. |
UNAUTHORIZED | 401 | On an end-user route, a user token that names no user — and, once enforced, a token issued to another client. See End-user authentication. A missing or unrecognised API key is FORBIDDEN. |
FORBIDDEN | 403 | API key is missing, isn’t recognised, or cannot access this project. The first two are rejected at the edge before the request reaches the application, so message — not code — is what distinguishes them. On any end-user route, also “User account not found. Complete registration first.” On the client plane (/clients/me), also “No active membership on this project” or “Insufficient permissions for this action”; the supplier plane answers those causes with NOT_A_MEMBER, MEMBERSHIP_INACTIVE or NO_SUPPLIER_ROLE instead. On POST .../events, a key without events:write. |
CAPABILITY_NOT_GRANTED | 403 | Your API key lacks Standard API access (*): its capabilities are empty or name only site events. Checked before the project or the user token. A project admin grants it on the Application. See Capabilities. |
ACTING_ROLE_NOT_HELD | 403 | An end-user request sent X-MB-Acting-Role naming a role the signed-in person doesn’t hold. Drop the header. |
MEMBERSHIP_INACTIVE | 403 | POST .../clients/me (onboarding) for a person whose access the business removed. Nothing was read or linked. The client asks the business to invite them again. See Build a booking flow. On the supplier plane, “Your access to this project has ended.”: the person’s membership ended, with every role removed. |
NOT_A_MEMBER | 403 | Supplier plane: “You are not a member of this project.” The signed-in person has no membership of the project — for example, an invited supplier who hasn’t accepted yet. See Supplier portal: refusals. |
NO_SUPPLIER_ROLE | 403, 404 | Supplier plane: “You don’t have supplier access on this project.” The person is an ACTIVE member but acts under no SUPPLIER role: it was removed, or they never had it. 403 where their roles lack the route’s permission, 404 where the permission passed but there is no supplier record to act on. Also 404 on the bookings routes for a request that sends X-MB-Acting-Role: CLIENT. See When access ends. |
SUPPLIER_NOT_LINKED | 404 | Supplier plane: “Your sign-in isn’t linked to a supplier record on this project.” The person holds SUPPLIER, but no single supplier record is linked to their sign-in. The business checks the supplier’s invitation. |
FIELD_NOT_SELF_EDITABLE | 403 | PATCH .../suppliers/me named a field only the business may change (active, email, externalId, externalData, maxTravelTime, defaultLocale). The whole body was refused. See Supplier portal: profile and photo. |
START_END_LOCATIONS_DISABLED | 422 | A supplier-plane schedule write set startLocation, endLocation, driveTiming or a maxTravelOn…Drive flag, and the project has start and end locations turned off: “Start and end locations are not enabled for this project, so startLocation cannot be set”. Nothing was written. Sending null, or the value already stored, is never refused. Leave the field out. See Supplier portal: availability. |
SETTING_NOT_DELEGATED | 422 | A supplier-plane schedule write set driveTiming, maxTravelOnStartDrive or maxTravelOnEndDrive, and the project hasn’t let suppliers choose that setting: “driveTiming is set by the project and is not delegated to suppliers”. Nothing was written. Hide the setting. |
INSIGHTS_DISABLED | 403 | The project has switched off this supplier insight (demand, or search). Hide the insight in your portal. |
NOT_FOUND | 404 | Resource doesn’t exist or has been soft-deleted. Also returned for a clientId or supplierId in the request body that belongs to a different project — never a 403, so a foreign id is indistinguishable from a missing one. |
UNRESOLVED_SUBDIVISION | 400 | The address state isn’t a recognised ISO 3166-2 subdivision of its country, and the offering or package prices by state or postal code there. message names the value and the subdivisions configured. Send the ISO code. See Regional pricing. |
INVALID_ORDER_ITEM_REFERENCE | 400 | POST .../bookings: the service line’s orderItemId isn’t an item of its orderId. Check both ids. |
REVIEW_ALREADY_EXISTS | 409 | POST .../bookings/{bookingId}/reviews: the booking already has a review in that direction. Don’t retry. |
INVALID_CURSOR | 400 | GET .../suppliers/me/alerts only: the cursor isn’t one this list issued, or came from another filter. Request the first page again without it. See Supplier portal: insights and alerts. |
VERSION_CONFLICT | 409 | Concurrent modification — re-read the resource and try again. Also a stale version on a supplier’s schedule, blocked time or travel zone, or another write landing on one during its DELETE. |
CONFLICT | 409 | Generic write conflict covering situations like a booking that’s already at capacity, or a client that’s already registered as a participant on it (see Group bookings and check-in). Also an ACTIVE schedule that overlaps another ACTIVE one, and DELETE .../suppliers/{supplierId} when the supplier’s sign-in changed during the delete — try again. Also a supplier photo confirmed or removed by another request while yours was saved, and PUT .../suppliers/{supplierId} when active changed between the update’s read and its write: read the supplier again and retry. message names the specific problem. |
SLOT_BOOKED | 409 | The supplier’s time is already taken by a confirmed booking. conflicts[] names the bookingId. Not retryable — search availability again. |
SLOT_HELD | 409 | The supplier’s time is claimed by a live hold — often your own. conflicts[] names the reservationId; convert it instead of booking directly. See Hold slots during checkout. |
OCCUPANCY_CONTENTION | 409 | Too many concurrent writes on one supplier’s day; the internal retry gave up. Retryable — resend after a short backoff. On POST .../holds/{reservationId}/release, the hold is still HELD (it still expires on its own): retry the release. |
PAYMENT_IN_FLIGHT | 409 | POST .../orders/{orderId}/payment-intent while a card payment on the order is already in progress (processing, or a saved-card charge). One open intent per order: “A card payment on order ord_… is already in progress. Wait for it to finish, then read the order’s transactions.” Don’t open another intent. Re-read the order’s transactions. See Accept payments with Stripe. |
ORDER_NOT_DELETABLE | 409 | DELETE .../orders/{orderId} on an order that holds a booking (booked or delivered) or a PENDING or SUCCEEDED payment or refund. message gives the counts. Nothing changed. Cancel the order with POST .../orders/{orderId}/status instead. See Orders. |
OFFERING_NOT_PRICED | 422 | The offering has no DEFAULT price rule, so nothing can be priced: “Offering has no DEFAULT price rule”. Any write that prices it can return this: order create, adding an order item, booking create, hold convert and package bookings. The business adds a DEFAULT rule. Don’t retry. |
NOT_A_PACKAGE_SERVICE | 400 | POST .../orders/{orderId}/package-bookings, its client-plane twin, or converting a hold against a PACKAGE item, when the item’s service has no active PACKAGE business model: “Service srv_… has no active PACKAGE business model”. The business turns one on. See Packages. |
ORDER_ITEM_BUSINESS_MODEL_MISMATCH | 400 | A booking line names a businessModelType its order item is not sold as, such as PACKAGE against a SINGLE_SESSION item. Send the kind the order item was sold as. See Bookings. |
TAX_MISMATCH | 400 | You sent tax on PATCH .../orders/{orderId}, and it is not both the tax the lines compute and the tax the order stores — or the order has lines in a different currency. Nothing was written. Omit tax: the platform computes it. See Orders. |
ORDER_NOT_SETTLED | 409 | You asked POST .../orders/{orderId}/status for PAID. An order becomes PAID only when its ledger covers its total. Record the payment instead of retrying. See Orders. |
TRANSACTION_IDEMPOTENCY_RECORD_MISSING | 409 | An idempotencyKey matched an earlier recording whose row could not be read back. Terminal — do not retry. Re-read the order’s transactions and contact support with the requestId. |
NO_SESSION_CREDIT | 422 | creditTreatment was sent when cancelling a booking that holds no package credit. Nothing was cancelled. Resend without creditTreatment. |
NOT_SELLABLE | 422 | A booking, order, order item or hold conversion names a service that isn’t LIVE or was deleted, or an offering that isn’t ACTIVE. message says which, for example “Service srv_… is DRAFT and is not sold; only LIVE services take new bookings and orders”. Nothing was written. A booking, hold conversion or package session against an order item already bought checks only the offering: the item stays bookable after its service stops being LIVE, but not after its offering stops being ACTIVE. Don’t retry. Offer another service. |
PACKAGE_NOT_ACTIVE | 422 | POST .../orders: a PACKAGE line names a package that is DRAFT or ARCHIVED. Nothing was written. Sell only ACTIVE packages. |
ORDER_NOT_PAYABLE | 422 | POST .../orders/{orderId}/transactions: a PAYMENT or COMP on a CANCELLED order: “Order ord_… is CANCELLED and cannot take a payment”. A REFUND is still recorded. Don’t retry. See Record offline payments. |
BOOKING_NOT_AMENDABLE | 422 | PATCH .../bookings/{bookingId} changed the time or supplier of a booking that is no longer SCHEDULED or STARTED. Nothing was written. Other fields can still be edited. See Bookings. |
BOOKING_NOT_DELETABLE | 422 | DELETE .../bookings/{bookingId} on a booking your key can’t cancel: it took place or was settled (AWAITING_CONFIRMATION, COMPLETED, a no-show). Nothing changed. Settle it instead. See Cancel or reschedule a booking. |
BOOKING_NOT_OPEN_FOR_PARTICIPANTS | 422 | Registering a participant on a booking that is no longer SCHEDULED or STARTED, or checking one in on a booking that is settled, disputed or cancelled. Nothing was written. See Group bookings and check-in. |
SERVICE_NOT_SOLD_AS | 422 | An order line implies a rate the service does not actively sell, such as a SINGLE_SESSION line on a service with no active SINGLE_BOOKING rate. Nothing was written. See Orders. |
PAYLOAD_TOO_LARGE | 413 | A site-events batch over 256 KB, or a beacon over 50 events or 64 KB. Nothing was read. Send fewer events per request. |
RATE_LIMITED | 429 | More than about 50 site-events requests a second from this key (bursts of 100). Retry the same batch after Retry-After. |
SERVICE_UNAVAILABLE | 503 | MarketBox couldn’t check or record a site-events batch. Nothing was recorded. Retry the same batch after Retry-After. |
INTERNAL_ERROR | 500 | An unexpected failure on our side. message is always “An unexpected error occurred”. Quote the requestId to support. See Retry guidance. |