Errors - Tickable API

Tickable uses regular HTTP status codes: 2xx means it worked, 4xx means something in the request needs fixing, 5xx means something went wrong on our side. Every error response has the same body:

{
  "error": {
    "type": "invalid_request_error",
    "code": "parameter_invalid",
    "message": "Invalid `limit`: Too big: expected number to be <=100",
    "param": "limit",
    "request_id": "req_3f2a9c1b7d4e4f0a8b6c5d2e1f0a9b8c"
  }
}

Field	Description
`type`	The broad category, see below. Branch on this.
`code`	A short, stable string for the specific error, e.g. `resource_missing`. Safe to branch on.
`message`	A human-readable explanation. Can change; do not parse it.
`param`	The parameter the error is about, when there is one.
`request_id`	Also sent as the `Request-Id` header on every response. Include it when you contact support.

Types

Type	Status	Meaning
`invalid_request_error`	400, 404	A parameter is missing or invalid, or the URL does not exist.
`authentication_error`	401	No credentials, or the API key or token is invalid or expired.
`permission_error`	403	The credentials are valid but lack a scope, e.g. `missing_scope`.
`not_found_error`	404	The resource does not exist or does not belong to your organization (`resource_missing`).
`idempotency_error`	400, 409	An `Idempotency-Key` problem, see Idempotent requests.
`api_error`	500	Something went wrong at Tickable. Safe to retry with the same `Idempotency-Key`.

Amounts

All amounts (price, total_price, refunded, …) are integers in cents, in EUR, including VAT: 2500 is €25.00.