
Recharge traffic is repetitive: the same plan lists are requested again and again. A little caching on your side makes your platform faster and your daily plan go further.
What is safe to cache
| Data | Suggested cache time | Why |
|---|---|---|
| Plan lists by operator and circle | 2 to 3 hours | Identical for every subscriber in a circle |
| DTH plan lists | 4 to 6 hours | Changes rarely |
| Operator and circle for a number | Up to 24 hours | Only changes when a number is ported |
| R-Offers for a number | About 10 minutes | Short-lived and personal |
| DTH balance and bills | Do not cache | Must always be current |
How daily limits work
Your plan includes a fixed number of quota-counted hits per day across Operator & Circle Fetch, Plan Fetch, R-Offer Check and the DTH endpoints. The counter resets at midnight India time. When it is full, calls return a clear daily limit reached message instead of data. Bill fetch runs on a separate wallet-based track and the code list endpoints are free.
Monitor before it hurts
- Call
usageStatusonce at start-up and show the remaining hits in your admin screen. - Alert your team at 80% of the daily limit.
- Check the API usage report in your dashboard for the busiest endpoints.
Cache keys that work
Build the key from the exact request: plans:A:49 for operator A and circle 49. Never include the customer's mobile number in a plan key, otherwise you will cache the same list thousands of times.
A note on our side
To keep responses fast, repeated identical lookups can be answered from a short server-side cache. Your daily hits are counted the same way, so caching on your side is still the best way to save hits.
Frequently asked questions
When does the daily counter reset?
At midnight India time. Every quota-counted call adds one to the day's total.
Can I see how many hits I have left?
Yes. Call the free usageStatus endpoint or open your dashboard.
Create an account, pick a plan and make your first call today. Every plan includes every endpoint.
Create account Read the docs


