Skydropx · Rate Limits

Skydropx Rate Limits

The Skydropx Pro API is rate limited to roughly two requests per second, and OAuth2 client-credentials access tokens are valid for about two hours before a new token must be issued. Clients should cache the Bearer token for its lifetime rather than requesting a new one per call, and should throttle request bursts to stay within the per-second limit. Fixed numeric per-endpoint quotas beyond the ~2 req/sec limit are not otherwise published.

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

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

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

Tagged areas include Shipping, Logistics, Multi-Carrier, Mexico, and Rate Limiting.

3 Limits Throttle: 429
ShippingLogisticsMulti-CarrierMexicoRate LimitingQuotas

Limits

Pro API Request Rate account
requests
~2 per second
Documented rate limit for the Skydropx Pro API.
Access Token Lifetime account
tokens
~2 hours per token
OAuth2 client-credentials access tokens expire after about two hours; re-issue via POST /oauth/token.
Classic API Request Rate account
requests
not published
No fixed numeric limit is documented for the classic Skydropx API (api.skydropx.com/v1).

Policies

Token Caching
Reuse a valid Bearer token across requests for its ~2 hour lifetime instead of requesting one per call.
Backoff Strategy
Throttle to stay under ~2 requests/second and apply exponential backoff with jitter, honoring Retry-After on 429 responses.

Sources