Skip to content
Last updated

Error Catalog

This document provides a comprehensive list of all error codes used in the Bookings API.

Format: RESOURCE-X-NNN

  • RESOURCE: 3-5 character resource identifier (AVAIL, OPRUL, BOOK, PMAP, VENUE, USER, IDENT)
  • X: Retryability indicator
    • R = Retryable (transient error, may succeed on retry)
    • N = Non-retryable (permanent error, requires different input)
  • NNN: 3-digit error code (001-999)

Error Response Format

All errors follow the RFC 7807 ProblemDetails format:

{
  "type": "https://tools.ietf.org/html/rfc7231#section-6.5.1",
  "title": "Error Title",
  "status": 400,
  "detail": "Detailed error message",
  "code": "RESOURCE-N-001",
  "isRetryable": false
}

Availability Errors (AVAIL)

Availability checking and product validation errors

CodeTitleDescriptionRetryable
AVAIL-N-001Product Not FoundThe requested product could not be found for the specified venueNo
AVAIL-N-002Venue Not Configured for PartnerThe venue is not configured for access by the current partnerNo
AVAIL-N-003No Products Available for PartnerNo products are accessible to this partner based on partner mappingsNo
AVAIL-N-004Venue Closed on Requested DateThe venue is closed on the requested date and cannot accept bookingsNo

Operator Rule Errors (OPRUL)

Operator availability rule validation errors

CodeTitleDescriptionRetryable
OPRUL-N-001Specific Date DisabledThe operator has disabled availability for the requested specific dateNo
OPRUL-N-002Date Range DisabledThe requested date falls within a date range disabled by the operatorNo
OPRUL-N-003Recurring Pattern DisabledThe requested date matches a recurring pattern disabled by the operatorNo
OPRUL-N-004Time Range DisabledThe requested start time falls within a time range disabled by the operatorNo

Partner Mapping Errors (PMAP)

Partner access and mapping validation errors

CodeTitleDescriptionRetryable
PMAP-N-001Venue Not Mapped to PartnerThe requested venue is not mapped to the current partnerNo
PMAP-N-002Product Not Mapped to PartnerThe requested product is not accessible to the current partnerNo
PMAP-N-003Partner Booking Access DeniedYou do not have permission to access this bookingNo
PMAP-N-004Partner Not FoundThe specified partner could not be foundNo

Booking Errors (BOOK)

Booking creation and management errors

CodeTitleDescriptionRetryable
BOOK-N-001No TMS Configurations FoundCannot perform any research for the provided venue group. No TMS configurations found.No
BOOK-N-002Booking Already ExistsThe booking already exists in the databaseNo
BOOK-N-003TMS Configuration Not FoundNo TMS configuration found for the specified composite IDNo
BOOK-N-004Missing Partner Source ConfigurationThe partner source is not configured for this venue group and partnerNo
BOOK-N-005Venue Group Partner Association Not FoundNo venue group and partner association foundNo
BOOK-N-006Booking Not FoundThe requested booking could not be foundNo
BOOK-N-007Preorder is requiredA preorder is required to proceed with this bookingNo

Venue Errors (VENUE)

Venue retrieval and management errors

CodeTitleDescriptionRetryable
VENUE-N-001Venue Not FoundThe requested venue could not be foundNo

Operator Errors (OPRTR)

Operator management and access errors

CodeTitleDescriptionRetryable
OPRTR-N-001Operator Not FoundThe requested operator could not be foundNo
OPRTR-N-002Operator Access DeniedYou do not have permission to access this operatorNo
OPRTR-N-003Partner Source RequiredThe partnerSource field is required when creating an operator as a partner userNo
OPRTR-N-004Operator Already ExistsAn operator with this name already existsNo
OPRTR-N-005Cannot Delete OperatorThis operator cannot be deleted because it has associated resourcesNo
OPRTR-N-006Invalid Operator ConfigurationThe operator configuration is invalid or incompleteNo
OPRTR-N-007TMS Credentials Already ExistsTMS credentials already exist for this operator and TMS combinationNo
OPRTR-N-008TMS Credentials Not FoundThe requested TMS credentials for this operator could not be foundNo
OPRTR-N-009Invalid TMS CredentialsThe TMS credentials could not be validated. Please check your configuration and try again.No

User Errors (USER)

User management and authentication errors

CodeTitleDescriptionRetryable
USER-N-001Email Already In UseA user with this email address already existsNo
USER-N-002User Not FoundThe specified user could not be foundNo
USER-N-003Invalid User CredentialsThe provided credentials are invalidNo
USER-N-004User Invite Not FoundThe user invitation could not be foundNo
USER-N-005User Invite Already AcceptedThis invitation has already been acceptedNo
USER-N-006User Invite ExpiredThis invitation has expiredNo
USER-N-007Invalid Venue Group AssignmentThe user cannot be assigned to the specified venue groupNo
USER-N-008Insufficient PermissionsYou do not have sufficient permissions to perform this actionNo
USER-N-009Invalid Role AssignmentThe specified role cannot be assigned to this userNo
USER-N-010User Account DisabledThis user account has been disabledNo
USER-N-011Invalid Email FormatThe provided email address format is invalidNo
USER-N-012Password Requirements Not MetThe password does not meet security requirementsNo
USER-N-013User Session ExpiredYour session has expired, please log in againNo
USER-N-014Maximum Login Attempts ExceededAccount locked due to too many failed login attemptsYes
USER-N-015Email Verification RequiredEmail address must be verified before proceedingNo

Identity Errors (IDENT)

Identity resolution errors

CodeTitleDescriptionRetryable
IDENT-N-001Invalid IdentityThe identity could not be resolvedNo
IDENT-N-002Invalid Partner ReferenceThe partner reference could not be resolvedNo

Sandbox Errors (SBOX)

Sandbox environment restriction errors

CodeTitleDescriptionRetryable
SBOX-N-001Not Available in SandboxThis endpoint is not available in the sandbox environmentNo

Validation Errors (VALID)

Request validation errors

CodeTitleDescriptionRetryable
VALID-N-001Validation FailedOne or more validation errors occurred.No

Additional Response Fields for VALID-N-001:

  • errors (object): Dictionary of field names mapped to arrays of validation error messages
    "errors": {
    "Date": [
      "Availability date cannot be in the past."
    ],
    "EndTime": [
      "EndTime must be after StartTime."
    ]

}



## FSEL Errors (FSEL)

Field selection (partial response) validation errors

| Code | Title | Description | Retryable |
|------|-------|-------------|-----------|
| `FSEL-N-001` | Unknown Field | One or more requested field names are not valid for this resource type | No |

**Additional Response Fields for FSEL-N-001:**

- **`invalid_fields`** (array): List of unrecognised field names
```json
"invalid_fields": [
"badField",
"unknownNested"
]
  • valid_fields (array): List of valid field names for the resource type

| FSEL-N-002 | Malformed Field Selection Syntax | The fields parameter contains malformed syntax (e.g. unmatched parentheses or empty field name) | No |

Rate Limit Errors (RATE)

API rate limiting errors

CodeTitleDescriptionRetryable
RATE-R-001Rate Limit ExceededToo many requests have been made in a short period. Please wait and retry.Yes

Migration from Old Error Codes

If you're migrating from the old error code format, here's the mapping:

Old CodeNew CodeNotes
USER001USER-N-001Email already in use
BOOKING001BOOK-N-001No RMS configurations
BOOKING002BOOK-N-002Booking already exists
BOOKING003BOOK-N-003RMS configuration not found
BOOKING004BOOK-N-004Missing partner source
BOOKING005BOOK-N-005Venue group partner association not found
OPERATOR_AVAILABILITY_DISABLEDOPRUL-N-001 to OPRUL-N-004Now split into 4 specific codes based on rule type
VENUE001VENUE-N-001Invalid pagination cursor
IDENTITY001IDENT-N-001Invalid identity
IDENTITY002IDENT-N-002Invalid partner reference

Retry Logic

Errors with isRetryable: true indicate transient failures that may succeed if retried:

  • Implement exponential backoff
  • Limit retry attempts (recommended: 3-5 attempts)
  • Examples: Rate limits (429), temporary service unavailability

Errors with isRetryable: false indicate permanent failures:

  • Do not retry with the same input
  • Modify request parameters or contact support
  • Examples: Invalid data (400), unauthorized (401), not found (404)

Support

For questions or issues with error codes, please contact api-support@bookingsgroup.com.


Last updated: 2026-03-11 16:13:49 UTC Version: 2.0 This file is auto-generated from ErrorCatalog.yaml - DO NOT EDIT MANUALLY