Turvo · Rate Limits

Turvo Rate Limits

Turvo does not publish fixed numeric rate limits for its Public API in openly accessible documentation; specific throttles are defined per tenant and surfaced in the tenant-gated API reference. Turvo does provide bulk endpoints that accept thousands of records in a single call, which is the recommended pattern for high-volume synchronization rather than issuing many single-record requests. Real-time change notification is delivered by webhooks (server push to a subscriber URL), reducing the need for aggressive polling. Clients should implement backoff and honor any 429 responses.

Turvo Rate Limits is the machine-readable rate-limit profile for Turvo on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests, records, and events.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Logistics, TMS, Freight, Rate Limiting, and Quotas.

3 Limits Throttle: 429
LogisticsTMSFreightRate LimitingQuotas

Limits

Public API Requests tenant
requests
not published
No fixed numeric request-rate limit is published publicly; defined per tenant.
Bulk Endpoint Batch request
records
bulk (thousands per call)
Bulk endpoints accept large batches in one call; preferred over many single-record requests.
Webhook Delivery subscription
events
event-driven
Webhooks push notifications to a subscriber URL on shipment, order, and tracking changes.

Policies

Bulk Preferred
Use bulk endpoints for high-volume synchronization instead of many single-record calls.
Webhook Over Polling
Subscribe to webhooks for status and location changes rather than polling list endpoints.
Backoff Strategy
Implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources