Skip to main content
The API is rate-limited. Integrations should control request frequency and concurrency, use pagination for large collections, and cache data that changes infrequently.

​
Throttling

If a request receives 429 Too Many Requests, pause further requests before retrying. If the response includes Retry-After, wait for the specified interval or time; otherwise use increasing delays with random jitter and a bounded retry count. Questions about sustained high request volume can be sent to hi@nonce.app. Include the endpoints, expected request frequency, and typical response size, but no credentials.

​
Temporary failures

Read requests can be retried after network failures or temporary server errors using bounded exponential backoff. Read-only POST searches fall into this category as well; the operation’s behavior matters more than its HTTP method. A timeout does not prove that a write failed. Repeating a request that creates a task batch may dispatch the same operation to miners twice. Check whether the task batch already exists with List Task Batches before deciding whether to resubmit.

​
Other errors

Avoid automatically retrying 400, 401, 403, or 404 responses. Check the request, credentials, and resource access first; see Authentication and access for access errors and Requests and responses for the error body.