MarineTraffic · Rate Limits

Marinetraffic Rate Limits

MarineTraffic's public service documentation portal (servicedocs.marinetraffic.com) describes authentication via API key but does not publish per-second, per-minute, or per-month request limits; consumption is governed by the credit pack purchased and any per-endpoint frequency restrictions agreed in contract. With MarineTraffic now operated by Kpler, rate-limit policies are effectively contract- scoped and not externally visible. This artifact records that absence rather than fabricating numbers.

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

It captures 2 rate-limit definitions, measuring varies.

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

Tagged areas include AIS, Maritime, Shipping, Vessel Tracking, and Rate Limiting.

2 Limits Throttle: 429
AISMaritimeShippingVessel TrackingRate Limiting

Limits

Per-account credit consumption account
varies
see contract / credit pack
Consumption is metered against a prepaid credit balance; per-endpoint frequency caps are set contractually rather than as a published RPS.
Per-endpoint polling cadence account/endpoint
varies
see endpoint update frequency
Each endpoint (PS01, VI01, EV01, etc.) has a natural refresh cadence; polling faster than that cadence wastes credits and may be throttled at the gateway.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter on 429 / 503 responses and honor Retry-After when present.
Credit-Based Throttling
The primary throttle is credit balance, not RPS. Exhausting credits returns an account- level error rather than a transient 429.
Contract-Scoped Limits
Hard limits are negotiated as part of the commercial agreement; verify ceilings with the account team before scaling consumption.

Sources