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, 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 and forbidden.

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

2 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-12.
Written by API Evangelist on 2026-07-12 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/wakeo-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.