Parcel Perform · Rate Limits

Parcelperform Rate Limits

Parcel Perform does not publish fixed numeric rate limits for the public API Guides & Reference. Access is gated behind an OAuth2 client-credentials Bearer token issued per contracted account, and the underlying commercial agreement (rather than a documented per-minute/per-day request cap) determines how much shipment, event, return, and webhook traffic an account can generate. The Bearer access token itself is reported to expire after 3600 seconds (60 minutes) and must be refreshed via the token endpoint.

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

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

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

Tagged areas include Logistics, Shipment Tracking, Rate Limiting, and Quotas.

3 Limits Throttle: 429
LogisticsShipment TrackingRate LimitingQuotas

Limits

API Requests account
requests
not published
No fixed numeric request-rate limit is documented in the public API Guides & Reference.
Bearer Access Token Lifetime token
seconds
3600
Reported token lifetime (60 minutes) before a new token must be requested via client-credentials grant.
Outgoing Webhook Delivery subscription
events
not published
No documented delivery-rate cap or retry/backoff schedule found for outgoing Shipment Tracking Update webhooks.

Policies

OAuth2 Token Refresh
Clients must re-authenticate via the client-credentials grant once the Bearer access token expires (reported 3600 seconds) rather than relying on a refresh token.
Backoff Strategy
As with most REST APIs, clients should implement exponential backoff with jitter and honor 429/5xx responses, even though Parcel Perform has not published explicit numeric thresholds.

Sources