Portcast · Rate Limits

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, conforming to the API Commons Rate Limits specification.

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

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.

2 Limits Throttle: 429
Supply ChainContainer TrackingLogisticsPredictive ETAOcean FreightRate LimitingQuotasThrottling

Limits

API Requests account
requests
see provider agreement
Per-account request throttling governed by subscription; not publicly published.
Tracked Shipments account
shipments
per subscription
Volume of concurrently tracked shipments/containers is set by the plan.

Policies

Push Over Poll
Register an HTTPS callback_url so updates arrive as webhooks instead of polling the tracking endpoints.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources