Shippeo · Rate Limits

Shippeo Rate Limits

Shippeo does not publish fixed numeric API rate limits in public materials. Any per-application throttling, quotas, or fair-use limits are documented in the login-gated developer portal and governed per contract / per application (clientID). Standard HTTP 429 handling with exponential backoff should be assumed for a production integration.

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

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

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

Tagged areas include Supply Chain, Transportation Visibility, Logistics, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Supply ChainTransportation VisibilityLogisticsRate LimitingQuotas

Limits

API Requests application
requests
not published
No fixed numeric request-rate limit is publicly documented; governed per application / contract.
Position Feed application
positions
not published
Carrier position submission throughput is not publicly documented.
Events-out Webhooks subscription
events
not published
Outbound webhook delivery volume follows tracked-transport activity; no public cap documented.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Webhook Retries
Outbound Events-out webhooks should be treated as at-least-once; receivers should be idempotent and return 2xx promptly.

Sources