Wise · Rate Limits

Wise Rate Limits

Wise does not publish a fixed numeric request-per-second rate limit for the Platform API. Limits are applied at the account level and adjusted dynamically based on usage patterns and risk signals. Excessive request volume returns HTTP 429 Too Many Requests and integrators are expected to honour Retry-After. Webhook delivery is retried with exponential backoff. Reconciliation against a published numeric ceiling pending - Wise asks partners with high-volume needs to coordinate via account management.

Wise Rate Limits is the machine-readable rate-limit profile for Wise on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests and events.

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 3 backoff/retry policies defined and response codes documented for throttled and serverError.

Tagged areas include Payments, FX, Cross-Border, Banking, and Multi-Currency.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-05-08.
Written by API Evangelist on 2026-05-08 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
PaymentsFXCross-BorderBankingMulti-CurrencyRate LimitingThrottling

Limits

Account-Level Throttle account
requests · minute
dynamic
Wise applies dynamic per-account limits. There is no public RPS ceiling. Partners requiring elevated throughput coordinate via account management.
Authentication Endpoints client
requests
tighter than data endpoints
Token issuance and OAuth endpoints are throttled more aggressively than data endpoints to deter credential stuffing.
Webhook Delivery subscription
events
best-effort with retry
Failed webhook deliveries are retried with exponential backoff for up to ~14 attempts before the subscription is marked unhealthy.

Policies

429 Throttling
When the dynamic account-level threshold is exceeded the API returns 429 Too Many Requests. Clients should respect any Retry-After header.
Backoff Strategy
Implement exponential backoff with jitter for both 429 and 5xx responses; cache idempotent reads (profiles, recipients, currencies) to reduce volume.
Idempotency
Use the X-idempotence-uuid header on transfer creation and funding calls so retries do not create duplicate money movements.

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/wise-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.