Errors

Errors use HTTP status codes and a JSON body with a single error object:

{
  "error": {
    "type": "invalid_request",
    "code": "invalid_parameter",
    "message": "Parameter 'from' must be a date in YYYY-MM-DD format.",
    "param": "from",
    "request_id": "0HNF8K3QJL2VM:00000001"
  }
}

Field	Description
`type`	Broad class: `invalid_request`, `authentication`, `not_found`, `rate_limit`, `server`.
`code`	Stable machine-readable reason. Branch on this, not on `message`.
`message`	Human-readable explanation. Wording can change.
`param`	The query or path parameter at fault, when there is one.
`request_id`	Quote this when contacting support.

Codes

Status	`type`	`code`
`400`	`invalid_request`	`invalid_parameter`, `invalid_cursor`, `limit_out_of_range`, `invalid_expand`, `as_of_in_future`
`401`	`authentication`	`unauthorized`
`403`	`authentication`	`forbidden`
`404`	`not_found`	`resource_not_found`
`422`	`invalid_request`	`too_many_groups`, `period_too_long`
`429`	`rate_limit`	`rate_limited`
`500`	`server`	`internal_error`

Reports that ask for too much

A report may compute at most 1000 rows. period_too_long is raised from the window and interval alone; too_many_groups after grouping. The message names what the request would produce and the ceiling:

{
  "error": {
    "type": "invalid_request",
    "code": "too_many_groups",
    "message": "Grouping by counterparty over this period produces 1240 groups. The maximum is 1000. Narrow the period or the filters.",
    "param": "group_by",
    "request_id": "0HNF8K3QJL2VM:00000001"
  }
}

Reports are never partial. A request either returns a complete answer or fails.

Rate limits

Each key may make 120 requests a minute. Requests without a valid key share 60 a minute per IP address. Every request counts as one, whatever its page size, so paging with limit=500 is the cheapest way to pull large ranges. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. A 429 also carries Retry-After. Both Reset and Retry-After count the seconds until the minute resets.

Unknown ids

Fetching an id that does not exist in the key’s workspace returns 404, including ids that exist in another workspace. The API never confirms the existence of data you cannot read.

Getting started

MCP

REST API

API reference

Codes

Reports that ask for too much

Rate limits

Unknown ids

​Codes

​Reports that ask for too much

​Rate limits

​Unknown ids

Codes

Reports that ask for too much

Rate limits

Unknown ids