Skip to main content

​
Rate Limits

Benefits of OAuth App Approval
  • 100x higher rate limits – Scale without worrying about throttling
  • Marketplace listing – Get discovered in the OrbitForms directory
  • Priority support – Direct access to our developer relations team
Learn about the review process →
Need higher limits for your use case? Contact us at support@orbitforms.ai to discuss custom rate limits for your application.

​
Write and import limits

Reads count against the per-minute limits above. Writes have their own buckets: A migration should use the imports: 1,000-row batches move 100,000 records an hour, where single creates would take days. See Migrating from another CRM.

​
Handling Rate Limits

429 Too Many RequestsWebhook creation has its own limit: 60 an hour per app per workspace while an app is in development, 500 once it is approved, and 60 an hour per workspace for API keys. POST /api/v1/webhooks answers with RateLimit-Limit and RateLimit-Remaining, and a 429 adds RateLimit-Reset. Pause and resume a webhook with PATCH is_active instead of deleting and re-creating it.When you exceed the rate limit, you’ll receive a 429 response with a Retry-After header. Implement exponential backoff:
  1. Wait for the time specified in the Retry-After header
  2. Or implement exponential backoff (1s, 2s, 4s, 8s…)
  3. Maximum retry time should be capped at 60 seconds

​
Best Practices

  • Cache responses when possible to reduce API calls
  • Use webhooks instead of polling for real-time updates
  • Batch operations when the API supports it
  • Monitor your rate limit headers proactively
Next: Webhooks →