Decisiv · Rate Limits
Decisiv Rate Limits
Decisiv Rate Limits is the rate-limit profile for Decisiv on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Limit state is signalled in the rate_limit_headers, retry_after, observed, and note response headers.
Tagged areas include Company, commercial-vehicle, Fleet Management, service-relationship-management, and Telematics.
0 Limits
rate_limit_headersretry_afterobservednote
Transcribed from the provider's documentation on 2026-08-12 — openapi/_original/*.json (429 responses), api-docs.decisi....
View Source
Limits
Decisiv publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Decisiv publishes NO numeric rate limit. 429 Too Many Requests is declared on 37 SRM Gateway operations and the response body is documented verbatim, but nowhere in the six harvested specs or on the developer documentation site is there a request-per-window figure, a burst allowance, a per-key or per-account scope, or a RateLimit-*/X-RateLimit-*/Retry-After response header. The only published guidance is prose inside the 429 description: throttling is "associated as a result of an over abundance of calls by a specific Application, Account, or IP Address resulting in a required cool off period" — which does name the three scopes the limiter uses, but attaches no number and no duration to any of them. An automated consumer therefore has no runtime signal at all: it cannot see its remaining budget, cannot learn when the window resets, and cannot be told how long the cool-off is. It can only discover the limit by hitting it, and then must guess at the backoff.
Companycommercial-vehicleFleet Managementservice-relationship-managementTelematicsAsset Managementmaintenance-and-repairHeavy Duty TruckingTransportationDealer ManagementJSON:APIWebhook
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.