Mono · Rate Limits

Mono Co Rate Limits

Mono enforces per-application throttling on its REST API, scoped by the secret application key passed in the mono-sec-key header. Specific requests-per-minute and daily quotas are not published in the public documentation and vary by environment (test vs live) and account agreement; they are not reconciled in this artifact.

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

It captures 3 rate-limit definitions, measuring requests.

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

Tagged areas include Open Banking, Financial Data, Payments, Direct Debit, and Africa.

3 Limits Throttle: 429
Open BankingFinancial DataPaymentsDirect DebitAfricaRate LimitingQuotasThrottling

Limits

Requests Per Minute application
requests
see provider documentation
Per-application throttling keyed on the mono-sec-key; value not published.
Data Pull Frequency account
requests
see provider documentation
Connect data endpoints (transactions, statements) may be cached or rate-limited per linked account; real-time pulls use x-real-time headers.
Test vs Live application
requests
see provider documentation
Test keys may carry separate, lower limits than live keys.

Policies

Per-Application Throttling
Limits are applied against the secret app key; separate keys for test and live environments.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429.

Sources