← Slimpay.ng

Used by every "Try It" panel across these docs to call app.slimpay.ng for real. Get one from Authentication — register or log in, then paste the token here. Stored only in this browser (localStorage), never sent anywhere but the Slimpay API, and auto-cleared after 8 hours.

Getting Started

Rate Limits

Every endpoint is rate-limited by group. Limits are tuned to what the endpoint does — brute-force-sensitive endpoints like login are much tighter than general reads.

GroupLimitApplies to
auth-strict5 / minute per IPLogin, register, password reset
otp3 / minute, 10 / hourPhone OTP send & confirm
pin5 / minute per userPIN verify & update
financial15 / minute, 100 / hourWallet ops, bill purchases, biller/school/payment-link checkout
api-authenticated60 / minute per userGeneral authenticated reads & writes
api-public100 / minute per IPPublic listings & lookups (schools, billers, banks)

When you exceed a limit

You'll get a 429 Too Many Requests response. The Retry-After header tells you how many seconds to wait before your next request will succeed.

bash
HTTP/1.1 429 Too Many Requests
Retry-After: 42
X-RateLimit-Limit: 15
X-RateLimit-Remaining: 0
Building a client

Back off using Retry-After rather than a fixed delay — limits vary significantly by endpoint group, and a login retry loop should behave very differently from a balance-polling loop.