Flinks Rate Limits
Flinks does not publish specific public per-endpoint rate limits. Throughput is governed by the customer contract and by the nature of the aggregation flow: an authorize token is valid for 30 minutes, long-running data calls (GetAccountsDetail / GetAccountsSummary) return HTTP 202 and must be polled via their Async variants roughly every 10 seconds up to a ~30-minute timeout, and cached (MostRecentCached) mode is recommended over live mode to reduce load on financial institutions. Specific numeric limits are not reconciled in this artifact.
Flinks Rate Limits is the machine-readable rate-limit profile for Flinks on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring minutes, seconds, and requests.
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 pending.
Tagged areas include Financial Data, Open Banking, Bank Aggregation, Fintech, and Canada.
generated, dated 2026-07-01.
Limits
Policies
Sources
- https://docs.flinks.com/reference/step-2-calling-for-data
- https://docs.flinks.com/reference/step-3-calling-for-pending-data
- https://docs.flinks.com/api/authorize/endpoints/authorize
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.