API Rate Limits

API Rate Limits

WRRK enforces rate limits to ensure fair usage and platform stability. Understanding rate limits helps you build reliable integrations.

Limits by Plan

Rate Limit Headers

Every API response includes rate limit information:

X-RateLimit-Limit: 500
X-RateLimit-Remaining: 487
X-RateLimit-Reset: 1711010460

• X-RateLimit-Limit — Your plan's maximum requests per minute.
• X-RateLimit-Remaining — Requests remaining in the current window.
• X-RateLimit-Reset — Unix timestamp when the limit resets.

When You Exceed the Limit

If you exceed your rate limit, the API returns:

HTTP 429 Too Many Requests

{
  "success": false,
  "error": {
    "code": "rate_limit_exceeded",
    "message": "Rate limit exceeded. Please retry after 23 seconds.",
    "retry_after": 23
  }
}

Best Practices

Implement exponential backoff: When you receive a 429 response, wait before retrying. Start with the retry_after value and double the wait time for each subsequent retry.

Cache responses: If you are fetching data that does not change frequently (e.g., contact lists), cache the response locally and refresh periodically instead of calling the API on every page load.

Use webhooks instead of polling: Instead of polling the API for changes, set up webhooks to receive real-time notifications. This dramatically reduces API calls.

Batch operations: Some endpoints support batch operations. For example, you can create up to 100 contacts in a single request using the batch endpoint:

POST /v1/contacts/batch

Monitor your usage: Track your API usage at Settings > API > Usage. Set up alerts to notify you when usage approaches your limit.

Requesting Higher Limits

Enterprise customers can request custom rate limits by contacting their account manager. Include your use case and expected traffic pattern.