Salt Edge · Rate Limits

Salt Edge Rate Limits

Salt Edge rate limits are negotiated per contract; sandbox keys are typically capped at 60 requests per minute. The PSD2 SCA cadence applies (typically 4 silent refreshes per consented user per 24h, with SCA required beyond). Throttled requests return HTTP 429.

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

It captures 3 rate-limit definitions, measuring requests_per_minute and refreshes_per_day.

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

Tagged areas include Open Banking and Rate Limiting.

3 Limits Throttle: 429
Open BankingRate Limiting

Limits

Sandbox per-minute client
requests_per_minute
60
Production per-minute client
requests_per_minute
-1
Per contract.
PSD2 SCA refresh per user end_user
refreshes_per_day
4
SCA required for 5th and beyond.

Policies

SCA Compliance
Honor PSD2 SCA cadence; trigger SCA flow when refresh limit is reached.
Backoff Strategy
Honor 429 Retry-After and apply exponential backoff with jitter.

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/salt-edge-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.