Loading...
Handle deployment-configured API limits with response headers, backoff, caching, and support escalation.
API rate limits protect platform stability and can vary by deployment and endpoint. Do not use an old plan table as a guarantee. Read the rate-limit headers returned by the API, respect HTTP 429 responses, and honor any retry-after value.
Use exponential backoff, cache data that does not change frequently, prefer webhooks where available, and batch supported operations. If your integration needs a higher limit, contact support@wrrk.ai with the endpoint, expected traffic, and use case.
Tags