Sendle · Rate Limits
Sendle Rate Limits
Sendle publishes one explicit rate limit (the tracking endpoint). Other endpoints do not document a numeric limit; integrators are expected to back off on 429 responses. Webhooks reduce the need to poll tracking and are the recommended way to receive ongoing updates.
Sendle Rate Limits is the machine-readable rate-limit profile for Sendle on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions.
Tagged areas include Shipping, Logistics, Last Mile, Parcels, and E-Commerce.
3 Limits
ShippingLogisticsLast MileParcelsE-CommerceCarbon NeutralSmall BusinessAustraliaUnited StatesCanada
Limits
{"period" => "second", "requests" => 10, "scope" => "per_ip"}
Sendle recommends polling each parcel at most once per hour. Higher limits are available on request via api@sendle.com.
{"period" => "minute", "requests" => "not documented", "scope" => "per_account"}
Sendle does not publish a numeric limit. Use Idempotency-Key on retries to avoid duplicate bookings.
{"period" => "minute", "requests" => "not documented", "scope" => "per_account"}
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.