Skip to main content
VitaRelay enforces rate limits per API key to ensure platform stability.

Limits

Rate limits are applied per API key, not per IP address.

Rate limit headers

Every API response includes headers showing your current limit status:
X-RateLimit-Reset is a Unix timestamp indicating when the window resets.

Handling 429 responses

When you exceed the limit, you’ll receive a 429 Too Many Requests response:
Implement exponential backoff with jitter:

Reducing request volume

  • Use webhooks instead of polling. Register a webhook endpoint for order.updated instead of polling GET /orders on a timer.
  • Batch where possible. If you’re syncing many patients, consider batching imports rather than creating one at a time.
  • Cache responses. Resource data that doesn’t change frequently (e.g. product catalog) can be cached locally.

Increasing your limit

Contact info@vitarelay.com if you need a higher rate limit for a high-volume integration.