Wakeo · Rate Limits

Wakeo Rate Limits

Wakeo does not publish numeric API rate limits; the API reference is password-protected. The production API at https://api.wakeo.co is fronted by AWS API Gateway (confirmed by live probe returning HTTP 403 ForbiddenException without a token), so per-key throttling and burst limits are technically possible and likely configured, but no specific request-per-second or daily quota figures are documented publicly. Practical throughput is more likely governed by the customer's contracted shipment volume than by a published per-minute request cap.

Wakeo Rate Limits is the machine-readable rate-limit profile for Wakeo 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 and forbidden.

Tagged areas include Supply Chain, Transportation Visibility, Logistics, Rate Limiting, and Quotas.

2 Limits Throttle: 429
Supply ChainTransportation VisibilityLogisticsRate LimitingQuotas

Limits

API Requests account
requests
not published
No fixed numeric request-rate limit is documented. AWS API Gateway fronting suggests per-key throttling may apply.
Tracked Shipment Volume account
shipments
per contract
Effective usage is bounded by the customer's contracted shipment/transport-mode volume rather than a per-minute request cap.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Authentication Required
Unauthenticated requests are rejected by AWS API Gateway with HTTP 403 ForbiddenException before any rate-limit accounting.

Sources