Parcels App · Rate Limits

Parcelsapp Rate Limits

Parcels App does not publish numeric per-second or per-minute request rate limits for the Parcels API v3. The operative limit is the monthly quota of unique tracking numbers (shipments) attached to your plan - 300, 500, or 1,000 per month on the published tiers - which GET /account reports as plan, limit, current, and resetDate. Because tracking is asynchronous, the documentation instructs clients to poll GET /shipments/tracking "every few seconds" by UUID until done is true, or to avoid polling entirely by supplying a webhookUrl. Repeated requests for an already-tracked number are served from cache and do not consume additional unique-shipment quota; only new unique tracking numbers count toward the monthly limit.

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

It captures 4 rate-limit definitions, measuring requests and shipments.

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

Tagged areas include Parcel Tracking, Shipment Status, Package Tracking, Rate Limiting, and Quotas.

4 Limits Throttle: not documented (business errors returned as JSON error fields)
Parcel TrackingShipment StatusPackage TrackingRate LimitingQuotas

Limits

API Request Rate account
requests
not published
No fixed numeric request-per-second or per-minute limit is documented.
Unique Tracking Numbers account
shipments
per plan (300 / 500 / 1000 per month on published tiers)
Each distinct tracking number added counts once toward the monthly plan limit; the counter and resetDate are exposed via GET /account.
Polling Cadence tracking request
requests
guidance - poll every few seconds
Documentation says to poll GET /shipments/tracking by UUID every few seconds until done is true, or use webhooks instead.
Tracking Request Batch Size request
shipments
not published
POST /shipments/tracking accepts an array of shipments (minItems 1); no documented maximum batch size.

Policies

Cached Results
Already-tracked shipments are returned immediately from cache (fromCache true), reducing both polling and quota pressure for repeat lookups.
Webhooks Over Polling
Supplying a webhookUrl shifts delivery to shipment_completed and batch_completed callbacks, eliminating the polling loop; failed webhook deliveries (timeouts, 4xx/5xx) may be retried.
Backoff Strategy
Clients should keep the documented few-second polling cadence, back off on pending (done false) responses, and stop polling a UUID once done is true or NO_REQUEST_FOUND is returned.

Sources