Okra · Rate Limits

Okra Africa Rate Limits

HISTORICAL. Okra did not publish fixed numeric per-minute rate limits for its public REST API. Practical throughput was governed by plan / billing-wallet balance (usage was pay-as-you-go per successful call) rather than a documented request-per-second cap, and by the availability of the underlying bank connections. Sandbox usage was unlimited and free. Numeric limits are not documented and could not be verified because the service is shut down (api.okra.ng no longer resolves).

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

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

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

Tagged areas include Open Banking, Open Finance, Nigeria, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Open BankingOpen FinanceNigeriaRate LimitingQuotas

Limits

Production API Requests account
requests
not published
No fixed numeric request-rate limit was documented; production usage was metered and billed per successful call.
Sandbox Requests account
requests
unlimited
Sandbox environment was free and unlimited for testing.
Billing Wallet Balance account
balance
prepaid
Production calls were settled from a prepaid billing wallet; an empty wallet effectively halted paid usage.

Policies

Retry / Backoff
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Auto Top-up
The Wallet API supported auto-top-up and threshold settings to avoid interruption when the billing wallet ran low.

Sources