A parameter is not valid

HTTP status 400

A query parameter has a value this endpoint does not accept.

From Pro up

One value in the request is not one this endpoint can use, so the API did nothing with the request. The parameter field of the problem names the value, and the detail field says what it accepts.

Why you get it

The usual cases:

• from or to is not a date written YYYY-MM-DD, to is later than today in UTC, or from is later than to.
• limit is not a whole number of at least 1. A number above 500 is not refused: the API lowers it to 500.
• cursor is not one the API gave out.
• A filter such as state, status, result or kind has a value that is not on its list. The detail gives the list.
• When you start an export, the body is not a JSON object, holds a field the endpoint does not know, or has no domain.

A from before the start of the organization's history is not an error. The API moves it up to the first day of the history.

What to do

1. Fix the value that the parameter field names, as the detail field says.
2. Pass next_cursor from the previous page unchanged, or leave cursor out to start again.
3. Leave out a parameter you do not need. Without from and to you get the last 7 days, ending yesterday in UTC. Without limit you get 100 rows a page.
4. Each endpoint's parameters and their values are in the OpenAPI document at /api/v1/openapi.json, which needs no token.

Published 27 October 2026 · Checked 27 October 2026