API rate limits and quota headers
How many requests per minute the Omnifox API allows depending on your plan, and how to read the quota headers.
Watch this step in the video · Pagination and limits
To protect the platform from abuse and keep good performance for everyone, every organization has a per-minute rate limit on the API, based on its subscription plan. The limit applies per (user + organization) or per token, depending on how you authenticate.
Limits by plan
| Plan | Requests / minute |
|---|---|
| Lite | 300 |
| Conecta | 600 |
| Crece | 1,200 |
| Escala | 2,400 |
| Exclusivo | Unlimited |
If your organization is on an unrecognized or trial plan, a safety cap of 300 req/min applies.
Quota headers
Every successful response includes:
X-RateLimit-Limit: your plan's cap (requests per minute).X-RateLimit-Remaining: how many requests you have left in the current minute.
When you exceed the limit, the API returns 429 Too Many Requests with:
Retry-After: seconds to wait before retrying.X-RateLimit-Reset: Unix timestamp when your quota resets.
Example: reading your remaining quota
curl -i -X GET "https://app.omnifox.io/api/v1/contacts" \
-H "Authorization: Bearer YOUR_TOKEN" | grep -i ratelimit
X-RateLimit-Limit: 600
X-RateLimit-Remaining: 587
Tips
- If your integration polls frequently (e.g. checking for new messages), prefer processing outbound Webhooks instead of polling the API at short intervals — it uses far less quota.
- Design your client to honor
Retry-Afterwith exponential backoff instead of retrying immediately.
Troubleshooting
- Constant 429s even though your volume is low: multiple processes or scripts may be sharing the same user/token; they all draw from the same bucket.
- Need more quota: upgrade your plan from Settings > Billing; the new limit takes effect automatically on the next minute boundary.
Related articles
-
How to connect integrations and external apps
Connect Omnifox with your favorite tools from the integrations catalog in just a few steps.
-
Integrations and API complete guide
Integrations and API in depth, in 30 chapters: API keys, real calls, signed webhooks, n8n, MCP and SDKs, all really working.
-
Connecting Omnifox to Azur, Siigo, Alegra, QuickBooks or another accounting system or ERP
Omnifox doesn't have a native connector for accounting systems or ERPs today. Here's how to connect them anyway with workflows, the HTTP node, n8n, Make, Zapier or the API, with examples.
-
Generate and use API keys and webhooks
Create API keys to access Omnifox programmatically and set up webhooks to receive real-time events.
-
Getting started with integrations (webhook / OAuth / API key)
Connect Omnifox with your other tools: what's available today, what's coming soon, and when to use a webhook, an OAuth connection or an API key.