Errors

Failed requests return a non-2xx status and a JSON body with an error message. Many errors also include a machine-readable code and, for validation failures, details.

{
  "error": "Validation failed",
  "code": "validation_failed",
  "details": [
    { "path": "year", "message": "Number must be greater than or equal to 1886", "code": "too_small" }
  ]
}

Status codes

Status	Meaning	What to do
`400`	The body is not valid JSON (`code: invalid_json`), or a request-specific rule failed.	Fix the request body.
`401`	Missing, malformed, invalid, revoked, or expired API key.	Check the header and that the key is still active.
`403`	The key lacks the required scope (`Missing scope: write:cars`), or the API is turned off for the team.	Create a key with the right scopes, or ask an admin to turn the API on.
`404`	The record does not exist or belongs to another team.	Check the ID.
`405`	The method is not supported on that path.	Check the endpoint reference.
`422`	Body or query parameters failed validation (`code: validation_failed`).	Read `details[]` — each item names the field `path` and the problem.
`5xx`	Something went wrong on our side.	Retry with backoff. If it continues, contact support.

Records from another facility always return 404, never 403, so the API does not reveal whether an ID exists on another team.

Get started

Cars

Customers

Contacts

Locations

Parking

Event types

Appointments

Communications

Marketing

Status codes

​Status codes

Status codes