Errors

Every error from the Tatallo PMS API has the same shape:

{
  "error": {
    "code": "property_not_found",
    "message": "Property not found.",
    "request_id": "385c1118-7082-4e15-97a7-16703f74d58b"
  }
}

Field	Meaning
`code`	A stable, snake_case code. Branch on this.
`message`	An English explanation for people, whatever your `Accept-Language`. It may change at any time: never branch on it.
`request_id`	The same value as the response’s `X-Request-Id` header. Quote it to support.

Codes

Status	`code`	Meaning	What to do
`400`	`invalid_limit`	`limit` is not a whole number from 1 to 100.	Send a `limit` from 1 to 100, or none for the default of 25.
`400`	`invalid_cursor`	`cursor` is not a cursor this key received: edited, built by hand, or issued to another key or environment.	Restart the walk without a cursor. See Pagination.
`401`	`unauthorized`	The key is missing, malformed, for the other environment, expired or revoked.	Check the key and the base URL. See Authentication.
`403`	`insufficient_scope`	The key is valid but lacks the scope the route needs.	Ask for a key with that scope.
`404`	`property_not_found`	The property is not connected to your PMS, or does not exist. Both get the same answer.	Use an `id` from `GET /v1/properties`.
`429`	`rate_limited`	Too many requests this minute.	Wait for `Retry-After` seconds. See Rate limits.

Codes never change meaning within /v1. New codes may be added for new situations, so handle an unknown code by its HTTP status.