Skip to main content
The API enforces per-key and per-IP rate limits to ensure fair usage.

Limits

Rate limit headers

When you approach the limit, responses include:

429 response

When the limit is exceeded:
The response includes a Retry-After header (in seconds) indicating when you can resume.

Tips

  • Cache template and record lookups on your side to reduce request volume
  • Use the /api/records/sync endpoint with a since timestamp for incremental updates instead of polling the full list
  • If you need higher limits, contact us