Errors & limits — Baydaar API
API v1 OpenAPIWebsite

Errors & limits

Status codes, the error format, caching and fair use.

Error format

Errors use a standard HTTP status and a JSON body:

{
  "error": {
    "code": "trip_not_found",
    "message": "No published trip with id 'x'."
  }
}
StatuscodeMeaning
400invalid_parameterA query parameter has a bad value; the message names it.
404trip_not_found, product_not_found, story_not_found, not_foundNo such trip or endpoint.
405method_not_allowedOnly GET is supported.
502upstream_errorCatalogue temporarily unavailable. Retry after a few seconds.
500internal_errorOur side. Retry; tell us if it persists.

Caching

Successful responses send Cache-Control: public, max-age=60 and an ETag. Cache for a minute or two on your server, and use If-None-Match to revalidate cheaply.

Fair use

There is no key and no hard quota today, but the API runs on shared infrastructure. Please cache, avoid polling more than once a minute, and don’t scrape every trip one by one when /trips returns them all. Heavy or abusive traffic may be blocked. If you need guaranteed volume, talk to us.

Using our content

Trip photos and text belong to Baydaar Experiences. You may show them to promote and link to Baydaar trips, as agreed with the team; please keep prices and dates as served and link to book_url for booking.