Skip to main content
Pikzels uses protective limits to keep service quality stable for all API users.
If request volume exceeds the active limit for your account or the platform, the API returns HTTP 429.

​
Behavior

  • Limits can apply to request rate, concurrent work, or temporary platform capacity.
  • Active limits can vary by account and may change over time.
  • HTTP 429 responses use the public error code TOO_MANY_REQUESTS.

​
Retry Guidance

  • Apply exponential backoff for 429 responses.
  • Add jitter to avoid synchronized retry spikes.
  • Keep client-side concurrency bounded for generation-heavy workflows.

​
Example Error Envelope

{
  "error": {
    "code": "TOO_MANY_REQUESTS",
    "message": "Too many requests. Please try again later."
  },
  "request_id": "18b2ad5e-2a9e-4d3f-b9a8-9f2a1e0b1234"
}
See /errors for the current error response format and common error codes.