The PureWL DPP API enforces rate limits to protect service stability. When you exceed a limit, the API responds with HTTP 429.
API requests are rate limited. If a request is rejected with HTTP 429, back off and retry with exponential backoff. Contact your PureWL account team for the limits on your account.

​
Client backoff guidance

Handle rate limiting defensively:
  • If a request is rejected for exceeding the rate limit, expect an HTTP 429 status.
  • Back off using an exponential backoff strategy (e.g., wait, then double the wait on each subsequent 429) rather than retrying immediately in a tight loop.
  • Batch or throttle high-volume workloads client-side rather than relying solely on server-side rejection as a throttle signal.
For general HTTP-level error handling beyond rate limiting, see Errors.

​
Next steps

Errors

See the full response envelope and status/error-code reference.

API Reference overview

Return to the full endpoint reference map.

Authentication

Refresh your Access Token before retrying after a rate-limit backoff.