Check remaining dynamic residential traffic by subtracting used bytes from the account limit. The platform counts 1 GB as 1,000,000,000 bytes, and usage stats can lag briefly. Not for mainland China.
After you buy dynamic residential traffic, check remaining quota from the account limit and usage, not from whether a single request succeeded. This page follows the official Dynamic Resource 2 guide: use `limitBytes - usedBytes` as remaining quota; `limitBytes`, `usedBytes`, and `todayUsedBytes` are all in bytes; the platform converts traffic with 1 GB = 1,000,000,000 bytes. Usage queries can lag for a short time.
This is not another billing-selection article; that guide is GB vs IP pricing. This page only covers how to reconcile traffic you already bought. Authorized targets only. Not supported in mainland China.
What to prepare
| Item | Where it comes from |
|---|---|
| Dynamic account ID and token | `accountId` from the purchase response; do not substitute an order number. See extract credentials |
| Account detail API | The documented account query returns limit, usage, usage today, and status |
| Optional usage series | Daily, hourly, or detail views; dates use `YYYY-MM-DD` |
| Wallet balance | Balance and top-ups are a separate ledger; see Balance and USDT top-up |
Placeholders only (not production): account ID example `ACCOUNT_ID_EXAMPLE`, token example `TOKEN_EXAMPLE_NOT_REAL`. Proxy placeholders such as `proxy.example.invalid` are not used to reconcile traffic.
How to read the fields
| Field | Meaning | How to use it |
|---|---|---|
| `limitBytes` | Total traffic limit, in bytes | Subtract usage to get remaining quota |
| `usedBytes` | Cumulative used traffic, in bytes | Do not rewrite the official conversion into a 1024-based gibibyte |
| `todayUsedBytes` | Traffic used today, in bytes | This is today only, not remaining quota |
| Remaining quota | `limitBytes - usedBytes` | Stop creating new tasks as you approach the limit, and consider buying more traffic |
| Stats lag | Usage rows can trail briefly | Trust the account difference for business decisions, even if one detail row is still missing |
Use the documented decimal GB: 1 GB = 1,000,000,000 bytes, not 1,073,741,824. Account status can be `active`, `paused`, or `disabled`. The docs state that an account that has already exhausted its traffic cannot be returned to `active`. Pause and resume follow the docs and the console.
Account query example
export ZTPROXY_BASE="https://backend.ztproxy.net/api"
export ZTPROXY_TOKEN="TOKEN_EXAMPLE_NOT_REAL"
curl "$ZTPROXY_BASE/business/dynamic-accounts/ACCOUNT_ID_EXAMPLE" \
-H "Authorization: Bearer $ZTPROXY_TOKEN"For daily or hourly usage, use the documented usage endpoint with a date range and paging. The `pageSize` range is in the docs (1 to 500). If the console also shows remaining traffic, follow the labels on screen and still cross-check the account fields.
What to do when quota is low
| Situation | What to do |
|---|---|
| Remaining quota is near zero, or extract says traffic is exhausted | Stop new tasks and buy more traffic; an exhausted account cannot be set back to `active` |
| A just-finished request is missing from the detail view | Read the account difference first; usage can lag briefly |
| Wallet balance is too low to buy more traffic | Top up first; see USDT top-up |
| You want to waste less traffic | Test connectivity before production requests, and do not retry unauthorized targets. Billing logic is in GB vs IP pricing |
Do not turn this page into a product concurrency cap or SLA. Client-side pacing still lacks independent product limits, so that topic stays on idea zt-88 and is not invented here.
Scope and compliance
Use this only against targets you are authorized to access. This is not a bypass guide. Prices follow the console and Pricing (dynamic about $0.40/GB, about $0.20/GB on the 100 TB package; shared static about $1.50 and dedicated about $5 per IP per month). USDT and USDC are accepted; Visa and Mastercard are still being applied for. Not supported in mainland China.
FAQ
How many bytes are in 1 GB here?
The official docs say the platform counts 1 GB as 1,000,000,000 bytes.
Why don't detail rows match remaining quota?
Usage data can lag briefly. Treat `limitBytes - usedBytes` as the remaining quota.
Is todayUsedBytes the remaining traffic?
No. It is only usage for the current day. Remaining quota is the limit minus cumulative usage.
Can I reactivate an account after traffic runs out?
The docs say an exhausted account cannot be returned to `active`. Buy more traffic first.
Is this the same as wallet balance?
No. Balance pays for new purchases or renewals. Dynamic traffic quota is the byte ledger for resources you already bought. Check both; do not merge them into one number.
Can I use this to bypass login walls?
No. Authorized targets only.
Do static IPs also consume GB?
Static residential IPs are billed per IP per month, which is a different model. See GB vs IP pricing and static.
Which price should I trust?
The console and Pricing.
Next steps
- Query account details and compute remaining quota.
- Stop new tasks and buy more traffic as you approach the limit.
- When you need to extract again, return to extract credentials.