Hatalar

No key, or the token does not resolve to one.

The key existed and was switched off. Issue a new one.

The key passed its expiry date. Issue a new one.

The month's searches and the search wallet are both used up. Buy a pack or wait for the reset.

The credential is fine, the source address is not on the key's allowlist.

The account's plan does not include API access at all.

The key is narrow and this endpoint is outside it.

The role bound to the key does not permit this operation.

The plan does not include this particular report.

The account has no active owner for the key to act as. The agency must fix this.

A traveller token was presented outside its own routes.

The account lacks an add-on this surface needs; `details.missing` names it.

No such record, or it belongs to another account.

The import entity key is not in the registry.

No operation by that id for this key: expired (a hold, ticket, release or purchase sent with an `Idempotency-Key` is kept 7 days, any other call 15 minutes), it can no longer be read, or another key's. On a hold, ticket or purchase, send the call again with the same `Idempotency-Key` and body; it replays the first answer or answers `booking_unresolved` with the booking its key claimed. Send a release again as it was. Do not refund the card on this answer alone.

The first call with this key is still running. Wait out `Retry-After` and send it again; once the first one is done the repeat replays its answer.

The fare moved. Price the offer again and confirm the new total with your customer.

The agency approves this ticket first. Call ticket again once it is approved.

The buyer's credit limit does not allow this hold.

The agency's balance with the supplier does not cover this ticket.

Some tickets of a multi-part journey were issued and one was not.

The hold is no longer open. Search again.

This booking can no longer be released here.

The agency has no supplier connection that can serve this call.

The supplier connection does not support this call.

The search or the offer has expired. Search again.

The record was rejected. `details` names the fields.

That key was already used for a different body or path.

The entity broadcasts and can be read, but cannot be pushed.

The ingest body carried no rows.

The batch is over the per-request row ceiling. Split it.

The account has no company to file the rows against.

The `branch_id` is not one of this account's. `GET /api/v1/workspace` lists them.

No such lead stage.

The lead could not be converted. Usually it already was.

The supplier refused the request; `details.provider_message` carries its reason.

The payment amount or currency differs from the booking total.

Name the POS the payment was taken on (`payment.merchant_account_id`).

This call moves money or seats and needs an `Idempotency-Key` header.

The price token is missing, expired or belongs to another offer. Price again.

The booking has no cari to bill and the payment needs one. Send `bill_to` with a VKN, a TCKN or a passport, or `customer_id`.

Too many calls in this window. Wait out `Retry-After`.

The supplier's answer is unknown, or the call did not finish in 3 minutes. Read the booking back (`booking_id`) and refund only if it was not ticketed. A hold, ticket or purchase keeps this answer under its `Idempotency-Key`; a new attempt takes a new key.

The suggestion engine could not answer. Transient.

The supplier could not be reached, the call could not be queued, or a search, price or rules call did not finish in 3 minutes. Nothing was booked, and a search costs nothing when this happens.