Error codes

What this covers

Every non-2xx response from travel.tech uses the error envelope described in
Errors: a
code, a human-readable message, and (for most codes) a recoveryAction
your integration can branch on. This page is the lookup table for every
code a partner-facing endpoint can return, its HTTP status, and what each
one means.

How it works

The code field always rides inside the error object:

{
  "error": {
    "code": "OFFER_EXPIRED",
    "message": "Human-readable description of what went wrong.",
    "details": [],
    "recoveryAction": "CHANGE_SELECTION",
    "retryAfterSeconds": null
  }
}

Branch your integration on code, not on message — message is
human-readable prose and may change between releases. code is a stable,
machine-readable contract.

What you need to handle

recoveryAction is omitted from a response when no recovery action applies
(for example, an authentication failure your integration resolves by
re-authenticating rather than retrying or correcting the request). The table
above shows "—" for those codes. A few codes choose their recovery action per
failure reason; the table shows "Varies by reason" and the response
carries the action to follow. A RETRY_NOW or RETRY_LATER action says a
retry can help, not that it is free of side effects: before you retry an
operation that charges or books, read
Idempotency and retries so a retry never
duplicates the booking or the charge. Here is what each published
recoveryAction value means:

Related guides

• Errors — the error envelope shape and
  validation details.
• Pagination — how paged lists work.
• Authentication — how UNAUTHORIZED and
  CONSUMER_AUTH_REQUIRED relate to your credentials.