Enums and error codes

Enums
Error codes

Reference data

Language codes

Supported language codes for API localization.

Code	Language
`EN`	English
`ES`	Spanish
`FR`	French
`IT`	Italian
`DE`	German
`PT`	Portuguese
`NL`	Dutch
`PL`	Polish
`KO`	Korean
`JA`	Japanese
`ZH_HANS`	Chinese (Simplified)
`ZH_HANT`	Chinese (Traditional)
`AR`	Arabic
`DA`	Danish
`NO`	Norwegian
`RO`	Romanian
`RU`	Russian
`SV`	Swedish
`TR`	Turkish

If a translation is not available for the requested language, content falls back to English (EN).

Currency codes

City codes

Supported cities are returned dynamically by the City API. This list may change over time, so always handle cities dynamically rather than hardcoding values.See: List Cities · List Collections · List Categories · List Subcategories · List Products

Media types

Supported media types in product details.

Type	Description
`IMAGE`	Image media
`VIDEO`	Video media
`PDF`	PDF document

See: List Products · Get Product

Product types

Supported product types within product details.

Type
`TOUR`
`ACTIVITY`
`EVENT`
`ATTRACTION`
`TRANSFER`
`AIRPORT_TRANSFER`
`ADD_ON`

See: List Products · Get Product

Listing price types

Pricing types used in product listings. The price type determines how inventory pricing is structured and how booking requests must be formed.

Type	Description
`PER_PERSON`	Price is charged per individual. Inventory returns person types (e.g., `ADULT`, `CHILD`, `SENIOR`) each with their own price point. The booking request must include one guest object per person with a valid `personType`.
`PER_GROUP`	A single price covers a group. Inventory returns pricing tiers by group size (e.g., 1-4 people = $100, 5-7 = $120, 8-10 = $150). The booking request does not require a `personType` per guest.

See: List Products · Get Product

Inventory types

Defines how a variant’s start time and duration are structured. This affects how startDateTime and endDateTime in inventory slots should be interpreted, and what kind of date/time picker to show the user.

Type	Description	Example
`FIXED_START_FIXED_DURATION`	Starts at a precise time and lasts a fixed duration. `startDateTime` = actual start, `endDateTime` = actual end.	A Broadway show at 7:00 PM lasting 2.5 hours
`FIXED_START_FLEXIBLE_DURATION`	Starts at a fixed time but the customer stays as long as they wish. `startDateTime` = entry time, `endDateTime` = venue closing time.	An observation deck visit with a timed entry slot
`FLEXIBLE_START_FIXED_DURATION`	Customer can arrive any time during operating hours but the experience lasts a fixed duration once started. `startDateTime` = opening time, `endDateTime` = latest allowed entry.	A hot-air balloon ride (1 hour) during a morning window
`FLEXIBLE_START_FLEXIBLE_DURATION`	Open entry and open-ended duration — customer arrives and leaves whenever they want within the day. `startDateTime` = opening time, `endDateTime` = closing time.	A theme park day pass

For FLEXIBLE_START_* types, startDateTime represents the opening time of the venue, not a specific entry time for the customer.

See: List Inventory

Inventory availability

Availability status within inventory slots, for inventorySelectionType: NORMAL products only. Determines whether and how many bookings can still be made for a given slot.

Status	Description
`LIMITED`	Limited spots remaining — check the `remaining` field for the exact count before booking.
`UNLIMITED`	No cap on bookings — the slot can be booked any number of times. `remaining` is a sentinel value (`1000`) and does not reflect a real count.
`CLOSED`	The slot is unavailable and cannot be booked.

SEATMAP products don’t return this status field — availability is expressed purely through remaining (top-level and per-section). See remaining count and availability status.See: List Inventory

Inventory selection types

Inventory selection types for booking interfaces.

Type	Description
`NORMAL`	Standard selection interface
`SEATMAP`	Seat map selection interface
`SVG`	Section-level selection on a venue map; seats are assigned automatically

See: List Inventory

Person types

Person types valid for booking variants.

Type
`ADULT`
`CHILD`
`INFANT`
`SENIOR`
`GENERAL`
`STUDENT`
`YOUTH`

Additional types such as RESIDENT, NON_EUR_CHILD, etc. may appear dynamically.

See: List Inventory · Create Booking · Get Booking — see Pax Types

Input fields

Input field types

Input field types for variant-specific customer information.

Field	Description
`NAME`	Customer name
`EMAIL`	Email address
`PHONE`	Phone number. Submit in international format with a leading `+` and country code (e.g., `+14155551234`)
`ADDRESS`	Address information
`AGE_`	Age-related fields
`COUNTRY_`	Country information
`DATE_OF_BIRTH_`	Date of birth
`DROP_OFF_LOCATION_`	Drop-off location
`FULL_NAME_`	Full name fields
`GENDER_`	Gender information
`IDENTITY_DOCUMENT_DETAILS_`	ID document details
`LANGUAGE_`	Language preference
`NATIONALITY_`	Nationality
`PASSPORT_DETAILS_`	Passport information
`PHYSICAL_INFORMATION_-_HEIGHT_`	Physical characteristics
`PICK_UP_DETAILS_`	Pickup information
`PICKUP_LOCATION`	Pickup location
`CUSTOM_*`	Custom dynamic fields provided by supply partners

Many more values may appear dynamically from supply partners. Always handle unknown values gracefully.

See: Get Product · List Inventory — see Input Fields

Input field data types

Data types an input field can have. Use this to drive form validation and rendering on your end.

Data Type	Description	Validation
`STRING`	Free-form text (e.g., `John Doe`)	`regex`, `minLength`, `maxLength`
`ENUM`	One of a predefined set of string literals (e.g., `MALE`, `FEMALE`, `OTHER`)	Must exactly match one of the allowed values
`BOOL`	Boolean flag — submit as the string `"true"` or `"false"`	—
`INT`	Whole-number value (e.g., `25`)	`minValue`, `maxValue`
`FLOAT`	Decimal number (e.g., `25.50`)	`minValue`, `maxValue`
`LOCATION`	Pickup or drop-off location — either a choice from predefined options or a free-form address	Predefined options, when present

There is no dedicated DATE dataType. Date and date-time fields (such as DATE_OF_BIRTH_*) are submitted as STRING, with the expected format enforced by validation.regex on the field.

Allowed values for ENUM and LOCATION fields arrive in the validation.values object, which has two different shapes depending on the endpoint — see Input field validation values.See: Get Product · List Inventory · Get inventory details

Input field validation values

validation.values carries the allowed values for ENUM and LOCATION fields. It has two shapes, and which one you get depends on the endpoint you called — not on the field’s dataType.

	Legacy shape	Current shape
Returned by	Get Product · List Inventory	Get inventory details
Found on	Variant-level `inputFields`	Inventory-level `inputFields`
`values` is	An array — of strings or of location objects	An object: `{ type, value }`
Option kind	Inferred from the sibling `dataType`	Read from `values.type`
No options	`values` is present, set to `null`	`values` key is omitted

Two traps when you add support for the current shape:

values is an object, not an array. A parser that assumes an array will break on it.
The values key is absent rather than null when there are no predefined options. Check the key exists before reading it.

ENUM fields

"values": ["VEGETARIAN", "VEGAN", "GLUTEN_FREE", "NONE"]

"values": {
  "type": "TEXT",
  "value": ["VEGETARIAN", "VEGAN", "GLUTEN_FREE", "NONE"]
}

The submitted value must exactly match one entry.

LOCATION fields with predefined options

Render the options as a dropdown and submit the selected location’s id or its displayName as the field value. Each object carries coordinates, an address, and optional timing constraints — see Predefined location objects for the full shape.

"values": [
  {
    "id": 24698,
    "displayName": "Bellagio",
    "address": "3600 S Las Vegas Blvd, Las Vegas, NV 89109, USA"
  }
]

"values": {
  "type": "PREDEFINED_LOCATION",
  "value": [
    {
      "id": 24698,
      "displayName": "Bellagio",
      "address": "3600 S Las Vegas Blvd, Las Vegas, NV 89109, USA"
    }
  ]
}

Branch on values.type, not on dataType. A supplier’s pickup-point list can arrive as an ENUM field with type: "TEXT" (plain names) or as a LOCATION field with type: "PREDEFINED_LOCATION" (structured objects) — values.type is the only reliable signal for which one you got.

Fields with no predefined options

STRING, INT, FLOAT and BOOL fields have no allowed-value list, and so does a LOCATION field that accepts a free-form address. The legacy shape reports this as "values": null; the current shape omits the key.

Legacy shape only — two edge cases that don’t apply to the current shape:

Predefined locations are only populated by Get Product. List Products doesn’t resolve them, so a LOCATION field there comes back with values: null even when the supplier has pickup points configured. Fetch the single product to get them.
null for other data types isn’t guaranteed. The legacy shape doesn’t gate on dataType, so a supplier-defined STRING or BOOL field carrying configured options can still emit a string array. Treat a non-null values as authoritative whatever the dataType says.

`values` object fields — current shape

Field	Type	Description
`type`	string	Discriminator for the contents of `value`. One of `TEXT` or `PREDEFINED_LOCATION`.
`value`	array	The allowed values. `string[]` when `type` is `TEXT`; an array of predefined location objects when `type` is `PREDEFINED_LOCATION`.

See: Get Product · Get inventory details

Predefined location objects

The location object used by LOCATION input fields that offer predefined pickup or drop-off points. The shape is identical in both validation.values shapes — the objects sit directly in the values array (legacy) or inside values.value when values.type is PREDEFINED_LOCATION (current).Submit either the selected object’s id or its displayName as the input field value when creating a booking.

Field	Type	Description
`id`	integer	Unique identifier for this location. Submit this value or the location’s `displayName` as the field value when creating a booking.
`latitude`	number	Latitude of the pickup/drop-off point in decimal degrees.
`longitude`	number	Longitude of the pickup/drop-off point in decimal degrees.
`address`	string	Full street address of the location.
`displayName`	string	Short human-readable label for display in a dropdown (e.g., `"Bellagio"`).
`timingConfig.startTime`	string \| null	Earliest pickup time for this location (HH:mm format). Null if no restriction.
`timingConfig.endTime`	string \| null	Latest pickup time for this location (HH:mm format). Null if no restriction.
`timingConfig.minPeriod`	integer \| null	Minimum notice required for this pickup in minutes. Null if no restriction.
`timingConfig.maxPeriod`	integer \| null	Maximum advance booking window in minutes. Null if no restriction.
`note`	object \| null	Additional instruction for this pickup location. Null if no note. Contains `content` (string) and `language` (language code).

Full location object

{
  "id": 480318,
  "latitude": 44.426767,
  "longitude": 26.102538,
  "address": "Bucharest, Romania",
  "displayName": "Z Executive Boutique Hotel",
  "timingConfig": {
    "startTime": null,
    "endTime": null,
    "minPeriod": null,
    "maxPeriod": null
  },
  "note": {
    "content": "",
    "language": "EN"
  }
}

See: Input field validation values · Get inventory details

Booking lifecycle

Cashback types

Cashback value types for promotional offers. The value field on the cashback object should be interpreted according to this type.

Type	Description	Example
`ABSOLUTE`	Fixed cashback amount in the product’s native currency	`value: 10` → customer receives $10 cashback
`PERCENTAGE`	Cashback as a percentage of the total variant price	`value: 10` → customer receives 10% of the booking total as cashback

See: List Products · Get Product

Booking status

Booking lifecycle statuses. PENDING and COMPLETED can still move to CANCELLED — e.g. customer cancellation within policy, or Headout-initiated cancellations like venue closures.

Status	Description
`UNCAPTURED`	Booking entry has been created but payment has not been captured. Does not lock inventory or price. Never sent via webhook.
`PENDING`	Payment captured. Booking is confirmed with the supplier — show it to the customer as confirmed. Ticket generation may still be in progress.
`COMPLETED`	Ticket has been generated and is available in the `tickets` array.
`CANCELLED`	Booking was cancelled — by the partner, customer, or Headout (e.g. venue closures). Reachable from `PENDING` or `COMPLETED`.
`FAILED`	Capture was attempted but rejected. The booking cannot move to any other status — create a new booking if the customer still wants to proceed.
`CAPTURE_TIMEDOUT`	`UNCAPTURED` booking was not captured within 1 hour and can no longer be captured. The booking cannot move to any other status — create a new booking if the customer still wants to proceed.

Transitions

From UNCAPTURED: remains UNCAPTURED until captured, → PENDING on successful capture, → FAILED on rejected capture, → CAPTURE_TIMEDOUT if no capture within 1 hour.
From PENDING: → COMPLETED when the ticket is generated, → CANCELLED if cancelled before fulfilment.
From COMPLETED: → CANCELLED if cancelled after fulfilment (e.g. venue closure).
From FAILED or CAPTURE_TIMEDOUT: no further transitions.

See: Create Booking · List Bookings · Get Booking · Update Booking · Create Webhook

Ticket types

Ticket delivery formats returned in the tickets array of a booking, and in ticketSection.tickets[].ticketType on the voucher response.

Type	Description	Example
`PDF_URL`	URL to a downloadable PDF ticket	View voucher
`HTML_URL`	URL to an HTML ticket page	View voucher
`QRCODE`	QR code data for scanning at the venue	View voucher
`BARCODE`	Barcode data for scanning at the venue	View voucher
`TEXT`	Plain text ticket information	View voucher

On the voucher response, branch your rendering on displayType rather than on this field. See Ticket display type.See: Get Booking · Get a voucher

Voucher booking status

Booking lifecycle states returned by the Get a voucher endpoint. Same vocabulary as Booking status on the booking endpoints, so the two never disagree.

Status	Description	`ticketSection` / `checkinButton`
`PENDING`	Payment captured — confirmed with supplier.	May be present
`COMPLETED`	Booking fulfilled.	May be present
`CANCELLED`	Booking cancelled.	Always null

Bookings that were never captured (UNCAPTURED, CAPTURE_TIMEDOUT) have no voucher and return 404.See: Get a voucher · Voucher API deep dive

Voucher template

The layout a voucher is meant to be rendered in.

Value	Description
`SINGLE_PAGE`	All voucher content fits on a single page or screen.
`MULTI_PAGE`	Voucher spans multiple sections or pages (longer layout).

Render the voucher in the template returned. Venue staff check vouchers against the layout they expect for that experience, so using the other template risks the guest being turned away at entry.See: Get a voucher

Address sequence type

Controls the shape of instructions.structured.location.addressGroups in the voucher response.

Value	`addressGroups` shape	Badge labels	Use case
`SINGLE_ADDRESS`	One flat group with all addresses	`"Option 1"`, `"Option 2"`, …	Customer can choose any one meeting point
`ALL_ADDRESS_ANY_ORDER`	One flat group with all addresses	`"Location 1"`, `"Location 2"`, …	Multiple relevant stops, any order
`ALL_ADDRESS_SPECIFIC_ORDER`	One group per route, each a sequential itinerary	`"Start Location"`, `"Location 2"`, …, `"End Location"`	Sequential multi-leg itinerary
null	Same grouping as `ALL_ADDRESS_SPECIFIC_ORDER`	`"Address details"` for all	No sequence set

See: Voucher API deep dive

Policy type

Returned in instructions.structured.policies[].type on the voucher response.

Value	Description
`BOOKING_AMENDMENT`	Whether and until when the booking can be cancelled or rescheduled.

The accompanying value is HTML and carries no heading of its own.See: Voucher API deep dive

Pickup drop-off type

Returned in bookingDetails.pickupDropoffLocation.pickupDropOffType on the voucher response, for transfer experiences. Null for everything else.

Value	Description
`PICKUP`	Pickup only — no drop-off is included, and `dropoff` is null.
`PICKUP_AND_DROPOFF`	Both a pickup and a separate drop-off. `dropoff` carries the drop-off location.
`PICKUP_SAME_AS_DROPOFF`	The guest is returned to the same place they were collected from.

See: Voucher API deep dive

Voucher exchange location type

Returned in instructions.structured.location.voucherExchangeLocationType on the voucher response. Indicates whether the voucher is exchanged at the activity venue or elsewhere. Applies to the location section as a whole, not to individual addresses.

Value	Description
`VENUE_LOCATION`	Exchange the voucher at the same location as the activity.
`DIFF_LOCATION`	Exchange the voucher at a different physical location from the venue.

See: Voucher API deep dive

Ticket display type

How to render a ticket entry. Drives UI rendering — branch on this instead of ticketType.

Value	How to render
`PDF`	Show a download button. Use `actionCta` as the button label; `url` as the download link.
`IMAGE`	Render `url` as a QR code or barcode image.
`TICKET_NUMBER`	Display `ticketCode` as a text confirmation code.
`NONE`	Do not render — unrecognized format.

See: Voucher API deep dive

Input field level

Defines who a given input field should be collected for. Use this to drive form rendering — only show and collect fields appropriate for each level.

Level	Description	Typical Fields
`PRIMARY_CUSTOMER`	Collected once, from the lead guest only. There is always exactly one primary customer per booking. Submit inside the `isPrimary: true` customer’s `inputFields`.	Name, email, phone, address
`ALL_CUSTOMER`	Collected from every guest in the booking, including the primary customer. Submit inside every customer’s `inputFields`.	Weight, height, meal preference, date of birth

level (who you collect from) and dataType (what shape the value takes) are independent axes — a LOCATION dataType field can be at any level.

See: Get Product · List Inventory

Cancellation reasons

Permitted cancellation reasons for partner cancellation requests.

Value	Description
`TICKETS_NOT_RECEIVED`	Tickets or voucher not received by the customer
`CHANGE_OF_TRAVEL_PLANS`	Customer changed travel plans
`MODIFY_EXISTING_RESERVATION`	Customer wants to modify an existing reservation
`FOUND_CHEAPER_OPTION_ELSEWHERE`	Customer found a cheaper alternative
`OTHER`	Other reason not listed above

See: Cancel Booking

Error code reference

Error code reference (JSON)

{
  "CAL_0000": "Unknown error occurred",
  "CAL_0100": "Unknown error occurred",
  "CAL_0101": "Tour information is not legitimate",
  "CAL_0102": "Tour or language does not exist",
  "CAL_0103": "Tour's addon does not exist",
  "CAL_0104": "Price information is not legitimate",
  "CAL_0105": "Itinerary item does not exist",
  "CAL_0106": "Price of the item has changed",
  "CAL_0107": "No ADULT in free booking",
  "CAL_0108": "Children not permitted without adult",
  "CAL_0109": "Minimum number of tickets not selected",
  "CAL_0110": "Maximum number of tickets exceeded",
  "CAL_0111": "Max 2 children per 1 Adult/Student/Senior",
  "CAL_0112": "Minimum number of pax not selected",
  "CAL_0113": "Maximum number of pax exceeded",
  "CAL_0114": "Book now pay later not eligible",
  "CAL_0120": "Slot not available anymore",
  "CAL_0121": "Tour not available anymore",
  "CAL_0122": "Pricing has changed",
  "CAL_0123": "Selected date-time closed or invalid",
  "CAL_0130": "Duplicate booking attempt within 30 min",
  "CAL_0200": "Unknown booking error",
  "CAL_0201": "Could not create booking, retry",
  "CAL_0202": "Reserved for use",
  "CAL_0220": "No recent order found",
  "CAL_0221": "Booking currency mismatch",
  "CAL_0222": "Itinerary vs booking currency mismatch",
  "CAL_0223": "Reservation failed via plugin",
  "CAL_0231": "Tour prices have changed",
  "CAL_0241": "Unsupported operation for API version",
  "CAL_0310": "City not found",
  "CAL_0600": "Incorrect user field",
  "CAL_0601": "Missing last name",
  "CAL_0602": "Missing mandatory user fields",
  "CAL_0603": "Invalid phone number",
  "CAL_0604": "Primary customer details missing",
  "CAL_0900": "Error in Calipso Product",
  "CAL_1000": "Valid API key not found",
  "CAL_1300": "Count doesn't match number of customers",
  "CAL_1400": "Invalid date range (from > to)",
  "CAL_1401": "Booking does not exist",
  "CAL_1402": "Could not fetch voucher; booking missing",
  "CAL_1403": "Unsupported itinerary type (combo)",
  "CAL_1404": "Authentication failed for voucher",
  "CAL_1405": "Temporary error fetching booking",
  "CAL_1406": "Booking does not belong to user",
  "CAL_1600": "Invalid body/query/path parameters",
  "CAL_1801": "Failed to cancel ticket",
  "CAL_1802": "Could not fetch booking (server error)",
  "CAL_1803": "Failed to reschedule booking",
  "CAL_1804": "Live inventory not available for reschedule",
  "CAL_1900": "Vendor audio guide not found",
  "CAL_1901": "Could not add audio guide",
  "CAL_1902": "Audio guide expired",
  "CAL_1903": "Share limit exceeded",
  "CAL_1904": "Audio guide unavailable",
  "CAL_1905": "Unsupported form type",
  "CAL_1906": "Non-nullable attribute is null",
  "CAL_1907": "Quote not found",
  "CAL_1908": "Tour user fields not found",
  "CAL-P0001": "Request body is not valid JSON",
  "CAL-P0002": "Method not allowed on this path",
  "CAL-P0003": "Unsupported Content-Type",
  "CAL-P0005": "A field failed validation",
  "CAL-P0006": "Unsupported event type",
  "CAL-P0007": "Endpoint URL rejected as unsafe",
  "CAL-P0008": "Subscription not found",
  "CAL-P0009": "Subscription limit reached",
  "CAL-P0010": "No such route",
  "CAL-P0011": "Temporarily unavailable",
  "CAL-P0012": "Temporarily unavailable",
  "CAL-P0013": "Unexpected failure",
  "CAL-9901": "No such route",
  "CAL-9904": "Unexpected failure"
}

Generic

Code	Description
`CAL_0000`	Unknown error occurred

Cart / itinerary

General

Code	Description
`CAL_0100`	Unknown error occurred

Legitimacy

Code	Description
`CAL_0101`	Tour information is not legitimate
`CAL_0102`	Tour or language does not exist
`CAL_0103`	Tour’s addon does not exist
`CAL_0104`	Price information is not legitimate
`CAL_0105`	Itinerary item does not exist
`CAL_0106`	Price of the item has changed
`CAL_0107`	No ADULT in free booking
`CAL_0108`	Children not permitted without adult
`CAL_0109`	Minimum number of tickets not selected
`CAL_0110`	Maximum number of tickets exceeded
`CAL_0111`	Max 2 children per 1 Adult/Student/Senior
`CAL_0112`	Minimum number of pax not selected
`CAL_0113`	Maximum number of pax exceeded
`CAL_0114`	Book now pay later not eligible

Expiration

Code	Description
`CAL_0120`	Slot not available anymore
`CAL_0121`	Tour not available anymore
`CAL_0122`	Pricing has changed
`CAL_0123`	Selected date-time closed or invalid

Duplicate Booking

Code	Description
`CAL_0130`	Duplicate booking attempt within 30 min

Booking

Pre Booking

Code	Description
`CAL_0200`	Unknown booking error
`CAL_0201`	Could not create booking, retry
`CAL_0202`	Reserved for use

Booking Results

Code	Description
`CAL_0220`	No recent order found
`CAL_0221`	Booking currency mismatch
`CAL_0222`	Itinerary vs booking currency mismatch
`CAL_0223`	Reservation failed via plugin

Expiration

Code	Description
`CAL_0231`	Tour prices have changed

Unsupported Operations

Code	Description
`CAL_0241`	Unsupported operation for API version

Fetch & Update

Code	Description
`CAL_1802`	Could not fetch booking (server error)
`CAL_1803`	Failed to reschedule booking
`CAL_1804`	Live inventory not available for reschedule

Rate limiting

Returned by Create a new booking (v1 and v2) when you exceed the request limit. This uses the error.code envelope, not a CAL_* code.

Code	Status	Description
`E_RATE_LIMIT_EXCEEDED`	429	Too many requests. Read the `retry-after` header (seconds to wait) before retrying

Other domains

Cancellation

Code	Description
`CAL_1801`	Failed to cancel ticket

Cities

Code	Description
`CAL_0310`	City not found

Customer fields

Code	Description
`CAL_0600`	Incorrect user field
`CAL_0601`	Missing last name
`CAL_0602`	Missing mandatory user fields
`CAL_0603`	Invalid phone number
`CAL_0604`	Primary customer details missing

Products

Code	Description
`CAL_0900`	Error in Calipso Product

Partner

Code	Description
`CAL_1000`	Valid API key not found
`CAL_1300`	Count doesn’t match number of customers

Reservations

Code	Description
`CAL_1400`	Invalid date range (`from > to`)
`CAL_1401`	Booking does not exist
`CAL_1402`	Could not fetch voucher; booking missing
`CAL_1403`	Unsupported itinerary type (combo)
`CAL_1404`	Authentication failed for voucher
`CAL_1405`	Temporary error fetching booking
`CAL_1406`	Booking does not belong to user

Malformed requests

Code	Description
`CAL_1600`	Invalid body/query/path parameters

Audio guide

Code	Description
`CAL_1900`	Vendor audio guide not found
`CAL_1901`	Could not add audio guide
`CAL_1902`	Audio guide expired
`CAL_1903`	Share limit exceeded
`CAL_1904`	Audio guide unavailable
`CAL_1905`	Unsupported form type
`CAL_1906`	Non-nullable attribute is null
`CAL_1907`	Quote not found
`CAL_1908`	Tour user fields not found

Event subscriptions

Returned by the event subscription endpoints, which document the full error envelope alongside each response.

Code	Status	Description
`CAL-P0001`	400	Request body is not valid JSON, or a field has the wrong type
`CAL-P0002`	405	That method is not supported on this path
`CAL-P0003`	415	Unsupported `Content-Type`. Send `application/json`
`CAL-P0005`	400	A field failed validation. `detailedMessage` names it
`CAL-P0006`	400	`eventTypes` contains an unsupported event type
`CAL-P0007`	422	Endpoint URL rejected as unsafe for delivery
`CAL-P0008`	404	No subscription with that id exists for your account
`CAL-P0009`	409	Subscription limit reached. `detailedMessage` carries the limit
`CAL-9901`, `CAL-P0010`	404	No such route, most often a missing trailing slash
`CAL-P0011`, `CAL-P0012`	502, 503	Temporarily unavailable. Retry with backoff
`CAL-P0013`, `CAL-9904`	5xx	Unexpected failure on our side

Start here

Build

Reference

Updates

Reference data

Input fields

ENUM fields

LOCATION fields with predefined options

Fields with no predefined options

`values` object fields — current shape

Booking lifecycle

Error code reference

Generic

Booking

Other domains

​Reference data

​Input fields

​ENUM fields

​LOCATION fields with predefined options

​Fields with no predefined options

​values object fields — current shape

​Booking lifecycle

​Error code reference

​Generic

​Booking

​Other domains

Reference data

Input fields

ENUM fields

LOCATION fields with predefined options

Fields with no predefined options

`values` object fields — current shape

Booking lifecycle

Error code reference

Generic

Booking

Other domains