Setting Up Auto-Topup So Client Bandwidth Never Silently Runs Out
A client's sub-user running out of allocated bandwidth mid-task doesn't fail gracefully from their side — it just stops working, usually at the worst possible moment. As a reseller, the first sign of that is often a support message, not a dashboard alert you saw coming. Auto-topup exists specifically to remove that failure mode.
How it works
Turning on auto-topup for a sub-user via `PATCH /api/v1/sub-users/:id/auto-topup` means that when the sub-user's remaining allocation drops to a threshold, additional bandwidth is drawn automatically from your own available stock and added to that sub-user's cap — no manual top-up call required, no window where the client's proxy is dead while you notice and react.
What this trades off
- →Auto-topup draws from your own stock, not the client's payment — if your billing arrangement with a client is prepaid-per-allocation, you need your own logic to reconcile "we auto-topped them up" against "did they actually pay for that yet"
- →It prevents the outage failure mode but doesn't prevent overspend on your side if a client's usage spikes unexpectedly — worth pairing with your own usage alerting, not treating as a fully hands-off setting for every client
- →For clients on a fixed monthly allocation you don't want silently exceeded, leaving auto-topup off and instead watching the usage endpoint is the more deliberate choice
Auto-topup on for clients you bill on ongoing/metered terms, where a live proxy matters more than a hard allocation ceiling. Off for clients on a fixed prepaid GB package, where you want to be the one deciding what happens when they hit the cap.
The request
curl -X PATCH https://globproxy.com/api/v1/sub-users/SUB_USER_ID/auto-topup -H "Authorization: Bearer YOUR_API_KEY" -d '{"enabled": true}'— GlobProxy API docs — Configure auto-topup
Frequently asked
Try it on 1 GB before you commit to more.
Non-expiring bandwidth, 195 countries, city-level targeting — from $4.50.
Get started →