Rate Limits

The Deliverty Hub API applies rate limits to ensure fair usage and platform stability. Limits are applied per API key (per channel).

Current Limits

Endpoint Category	Limit	Window
Task creation	100 requests	Per minute
Task queries (GET)	300 requests	Per minute
Task updates (PUT/PATCH)	200 requests	Per minute
Webhook subscriptions	30 requests	Per minute
All other endpoints	200 requests	Per minute

Rate Limit Headers

Every API response includes rate limit headers:

Header	Description
X-RateLimit-Limit	Maximum requests allowed in the current window.
X-RateLimit-Remaining	Number of requests remaining in the current window.
X-RateLimit-Reset	Unix timestamp when the current window resets.
Retry-After	Seconds to wait before retrying (only present on 429 responses).

When Limits Are Exceeded

When you exceed a rate limit, the API returns a 429 Too Many Requests response:

{
  "statusCode": 429,
  "message": "Rate limit exceeded. Try again in 45 seconds.",
  "error": "Too Many Requests"
}

Best Practices

• Monitor headers — check X-RateLimit-Remaining to proactively slow down before hitting limits.
• Implement backoff — on 429 responses, wait the duration specified in Retry-After before retrying.
• Batch operations — use bulk endpoints when available instead of individual requests.
• Cache responses — cache GET responses to reduce unnecessary API calls.
• Use webhooks — instead of polling for status changes, subscribe to webhook events.