Flinks · Rate Limits

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, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring minutes, seconds, and requests.

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.

4 Limits Throttle: 429
Financial DataOpen BankingBank AggregationFintechCanadaRate LimitingQuotasThrottling

Limits

Authorize Token Lifetime session
minutes
30
The flinks-auth-key token expires 30 minutes after generation.
Async Polling Cadence request
seconds
10
Poll the Async endpoint with the same RequestId roughly every 10 seconds while HTTP 202.
Async Request Timeout request
minutes
30
A pending data request times out after approximately 30 minutes.
Concurrency / Throughput account
requests
see contract
Contract-governed; not published publicly.

Policies

Cached Mode Preferred
Use MostRecentCached=true to serve cached data and avoid unnecessary live institution hits.
Async Polling
Honor HTTP 202 and poll the matching Async endpoint rather than retrying the synchronous call.
Backoff Strategy
Implement exponential backoff with jitter and honor Retry-After on HTTP 429.

Sources