Skip to main content

​
Pricing

Rangler API is billed per request: ₦1 per billable API request. A request is billable when it is made with a live key (rgl_live_) and returns: Sandbox requests (rgl_test_ keys) are never billed.

​
Access tiers

Tiers set your environments and service limits. They do not add charges on top of the per-request price. Production keys require live access.

​
Service limits

Each tier has operational limits on the units below. They are service limits, not separate billing units. If your usage approaches a service limit, you’ll see it in the portal and we’ll review the account with you. Rangler does not charge for workflow units when you go over a limit. Connect is design-partner/custom during v1. We meter link sessions, active connections, refreshes, connected accounts, retained history, and webhook deliveries, but we do not publish a self-serve Connect package until provider access and support costs are proven.

​
Request rate limits

Rangler enforces request rate limits separately from billing. Every API response includes rate-limit headers:
When you hit the request-rate limit, Rangler returns 429 Too Many Requests with a Retry-After header. Rate-limited requests are not billed. See Errors for the response format. Rate limits apply at the organization level. All keys in your organization share the same daily budget.

​
Checking your usage

The portal’s API usage page shows your organization’s requests by endpoint, request path, and API key, along with your billable live requests for the current month. Billing months run from midnight to midnight, West Africa Time (Africa/Lagos). Quickstart covers your first request, Authentication explains the API key model, Environments covers sandbox and live isolation, and Errors documents rate-limit headers and error responses.