Portcast Rate Limits
Portcast authenticates the Container Tracking API with an x-api-key header issued per account. Request throttling and tracked-shipment quotas are governed by the negotiated subscription rather than a public per-minute rate table. To avoid polling pressure, Portcast recommends registering a callback_url (Push API) so tracking updates are delivered as webhooks instead of repeated GET requests. Specific numeric rate limits are not publicly documented and are not reconciled in this artifact.
Portcast Rate Limits is the machine-readable rate-limit profile for Portcast on the APIs.io network, in the API Commons Rate Limits shape.
It captures 2 rate-limit definitions, measuring requests and shipments.
An exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Supply Chain, Container Tracking, Logistics, Predictive ETA, and Ocean Freight.
generated, dated 2026-06-21.
Limits
Policies
Sources
- https://portcast.stoplight.io/docs/portcast-api/
- https://portcast.stoplight.io/docs/portcast-api/dxd93fedun52o-push-api
- https://kb.portcast.io
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.