On this page

API rate limits

Noxtica limits how often a caller can use an operation. Limits depend on the operation and on your account, so this page describes the mechanism and does not list figures. Do not hard-code a limit: the response tells you when to try again.

What a limited request returns
How to retry

How this page is organisedBar length shows each section’s share of the text. Select a section to jump to it.

The response

The request is rejected with status 429 and a JSON body.

Read the Retry-After header for the number of seconds to wait.

Wait

Stop sending requests for the operation until the wait has passed.

Add random jitter to the wait.
Spread bulk work over time.

Retry

Retry only requests that are safe to repeat.

Send an Idempotency-Key where the operation accepts one.
Increase the wait after each further 429.

What to do when a request is rate limited

What a limited request returns

A request over its limit is rejected with HTTP status 429 and a JSON body. The Retry-After header holds the number of seconds to wait before the next request.

Header	Meaning
`Retry-After`	Seconds until the bucket allows another request.

Field	Type	Always returned	Description
`error`	string	No	Allowed values: `Rate limit exceeded`.
`retryAfter`	integer	No
`requestId`	string	No

Example body:

{
  "error": "Rate limit exceeded",
  "retryAfter": 1,
  "requestId": "req-test"
}

Header	Meaning
`Retry-After`	Seconds until the window resets.

Field	Type	Always returned	Description
`code`	string	Yes	Stable machine-readable identifier.
`error`	string	Yes
`message`	string	No
`requestId`	string	No

Header	Meaning
`Retry-After`	Seconds until the bucket allows another request.

Field	Type	Always returned	Description
`error`	string	Yes	Allowed values: `Rate limit exceeded`.
`retryAfter`	integer	Yes	Seconds to wait; equals the `Retry-After` header.
`requestId`	string	No

Example body:

{
  "error": "Rate limit exceeded",
  "retryAfter": 12,
  "requestId": "req-test"
}

How to retry

Stop sending requests for the operation until the Retry-After period has passed.
Retry the request once, then increase the wait on each further 429, with random jitter, up to a maximum you choose.
Retry only requests that are safe to repeat. For an operation that creates something, send an Idempotency-Key where the operation accepts one so a retry cannot create a second copy.
Spread bulk work over time instead of sending it in one burst.

This page is generated from the Noxtica OpenAPI specification release v0.4.0: kyc.yaml version 1.2.0-2026-10-27 (SHA-256 c91a695cfde0), mcp.yaml version 0.1.0-2026-10-27 (SHA-256 1a4875efa736), pulse.yaml version 0.9.0-2026-10-27 (SHA-256 95196a58bb5b), v1.yaml version 1.3.0-2026-10-27 (SHA-256 3fd15257a022). Do not edit it by hand.