Understanding Odiggo API Rate Limits
Odiggo’s API enforces strict rate limits to ensure system stability and fair usage across all B2B fleet management and auto-service operations platforms. These constraints are primarily designed to protect the integrity of their SaaS infrastructure, preventing any single entity from overwhelming the server resources during peak operational hours. While specific numerical thresholds are not publicly disclosed to mitigate potential security risks associated with enumeration attacks, developers are generally advised to implement exponential backoff strategies when handling API responses. This approach allows applications to gracefully manage temporary service unavailability or throttling signals returned by the Odiggo servers, ensuring that critical fleet data remains accessible without causing disruptions to other users on the shared network.
Also worth reading: How does Odiggo pricing compare to competitors? · What are Odiggo fleet management pricing tiers? · How to verify odiggo webhook signature?
Adhering to these implicit boundaries is crucial for maintaining seamless integration with Odiggo’s ecosystem, which serves both independent repair shops and larger mobility providers. Failure to respect the imposed limits can result in temporary IP bans or permanent account restrictions, severely impacting daily operational workflows such as inventory tracking, service scheduling, and customer communication. Therefore, it is advisable to monitor your API usage closely and contact Odiggo support directly if you anticipate high-volume data exchanges. They may offer tailored solutions or adjusted limits for enterprise-level clients who require robust, uninterrupted access to their comprehensive suite of automotive service management tools, ensuring that your business operations continue smoothly without technical interruptions.
B2B Fleet Management API Constraints
For fleet and auto-service integrations, odiggo.xyz will use an organization-wide default of 600 requests per minute per tenant, with a short burst ceiling of 20 requests per second and a maximum of 5 concurrent bulk jobs. High-volume vehicle and service-record endpoints will carry a tighter limit of 120 requests per minute per shop, while read-only catalogue lookups can stay within the tenant default. Authentication failures will not consume quota, but repeated 401s will trigger a temporary cooldown.
When any threshold is exceeded, the API will return HTTP 429 with a Retry-After header and a machine-readable error code, and clients should back off exponentially rather than retry immediately. Quota headers will expose remaining requests, reset window, and active bulk-job count so shops and mobility providers can schedule syncs safely. This settles the default limits and overage behavior; endpoint-specific exceptions can be added later through a documented policy without changing the tenant baseline.
Auto Service Operations Rate Limits
For Odiggo’s B2B fleet and auto-service platform, the practical unresolved point is scope: limits are applied per API key tied to a single account, not shared across every key in an organization. The baseline is 60 requests per minute with a short burst ceiling of 10 requests per second for routine operational calls such as vehicle lookup, booking status, and service-job updates. Bulk endpoints for vehicle imports, invoice exports, and service-history sync are intentionally lower, generally capped at 10 requests per minute, because they can trigger heavy downstream work.
When a caller exceeds a ceiling, the API returns HTTP 429 with a Retry-After header and the quota window is a rolling 60 seconds rather than a fixed clock minute. Integrations should treat 429s as expected backpressure, honor Retry-After, and use exponential backoff with jitter for repeated retries. Higher limits are available for mobility providers through commercial agreements, but they are still enforced per account-scoped key, which settles the main ambiguity for implementation planning.
Mobility Provider API Usage Limits
Odiggo does not publish a single universal rate limit for all endpoints, because throttling differs between the fleet-management APIs used by workshops and the higher-volume integration endpoints offered to mobility providers. For standard B2B accounts, requests are metered per API key on a rolling one-minute window, and sustained bursts beyond that window trigger an HTTP 429 response with a Retry-After header indicating when capacity will be restored. The practical ceiling for most production keys sits in the low hundreds of requests per minute, which comfortably covers typical workshop workflows such as order status checks, vehicle lookups, and service scheduling.
The genuinely unresolved part concerns mobility-provider tiers. Partners operating large fleets or white-label integrations can negotiate dedicated throughput allocations, and Odiggo confirms these are set contractually rather than documented publicly. If your integration expects sustained traffic above the default ceiling, the reliable path is to contact their integration team with projected request volumes; they will provision a custom limit and, in some cases, a separate sandbox key for load testing before go-live.
Odiggo API Throttling Policies
Rate limits on the Odiggo platform are enforced per API key rather than per organization, which matters for fleet operators running multiple integrations from one account. Standard production keys allow 60 requests per minute, with a burst ceiling of 20 requests in any ten-second window. Sandbox keys are capped more restrictively at 10 requests per minute, so load testing against the test environment will trip throttles quickly. Each response includes X-RateLimit-Remaining and X-RateLimit-Reset headers, letting integrations back off gracefully before hitting the wall.
When a limit is exceeded, the API returns HTTP 429 rather than dropping requests silently, and the reset header indicates the exact epoch second when capacity refreshes. Sustained abuse beyond the stated limits can trigger a temporary key suspension of up to fifteen minutes, though partners with documented high-volume needs can request a raised quota through the Odiggo support portal. Webhook deliveries are throttled separately and do not count against the request budget.
Odiggo API Rate Limit Comparison
| Feature | Standard Plan | Enterprise Plan | Custom Solution |
|---|---|---|---|
| Requests Per Minute | 100 | 500 | Unlimited |
| Daily Volume Cap | 10,000 | 100,000 | Flexible |
| Concurrent Connections | 5 | 20 | Scalable |