API problem types

Every error from the API is a JSON problem with a code field and a type address that ends in the same code. Open the type address and you land on the page for that code, in English or Finnish, whichever your browser asks for.

The title and detail fields are in Finnish when the request's Accept-Language header asks for it, and in English otherwise. The detail names the cause in your case, so read it before the page.

• The request has no valid token

  A 401 from the API: the token is missing, sent the wrong way, unknown or revoked. Check the Authorization header, then where the token came from.

• The token has expired

  A 401 from the API: the token passed the expiry date it was created with. An admin creates a new one, and you swap it into your script or tool.

• The plan does not allow this request

  A 403 from the API: the token is valid, but the plan or the token's own access does not cover the request. The detail names one of six causes.

• Nothing was found at this path

  A 404 from the API: the domain name or id in the path leads to nothing in the token's organization. Find the name or id in a list answer first.

• A parameter is not valid

  A 400 from the API: one value in the request is not one the endpoint can use. The parameter field names it, and the detail says what it accepts.

• The hourly request limit is used up

  A 429 from the API: the token has used every request its plan allows this clock hour. Wait the seconds in Retry-After, then send the request again.

• An export is already being built

  A 409 from the API: an export of the organization is still being built. Wait until its status is ready, then download it or start the next one.

• The export has expired

  A 410 from the API: the export's file passed its keeping time, so it is not handed out. Start a new export with the same choices and download it in time.

Published 27 October 2026 · Checked 27 October 2026