Authenticate, find products, create a ZTProxy order and retrieve proxy details.

English API Quickstart

Use the same API origin worldwide:

https://backend.ztproxy.net/api

1. Authenticate

curl -X POST "https://backend.ztproxy.net/api/auth/login" \
  -H "Content-Type: application/json" \
  -d '{"username":"your_username","password":"your_password"}'

Store data.token securely and send it as Authorization: Bearer <token>. Never put a token, site password or proxy credential in a client-side application, URL or support message.

2. Check the account

curl "https://backend.ztproxy.net/api/open/app/dashboard/info/v2" \
  -H "Authorization: Bearer $ZTPROXY_TOKEN"

Use this response to confirm the current balance and resource summary before creating an order.

3. Find a product and location

curl -X POST "https://backend.ztproxy.net/api/open/app/product/query-standard/v2" \
  -H "Authorization: Bearer $ZTPROXY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"proxyType":103,"language":"en"}'

Use the returned productId, countryCode and cityCode. Do not construct or guess internal product identifiers.

4. Create a static order

curl -X POST "https://backend.ztproxy.net/api/open/app/static/order/create-standard/v2" \
  -H "Authorization: Bearer $ZTPROXY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "orderType":"static_proxy",
    "poolId":"<productId>",
    "userId":1001,
    "countryCode":"US",
    "cityCode":"<cityCode>",
    "staticType":"isp",
    "ipCount":1,
    "cycleTimes":1,
    "duration":30,
    "unit":1,
    "unitPrice":0,
    "totalAmount":0,
    "remark":"API order"
  }'

An accepted request may return queued: true. Poll the order list for the final order state and assigned proxy details; acceptance is not proof of fulfilment.

5. Read static orders

curl "https://backend.ztproxy.net/api/open/app/static/order/list/v2?page=1&pageSize=10" \
  -H "Authorization: Bearer $ZTPROXY_TOKEN"

6. Create a rotating-proxy order

curl -X POST "https://backend.ztproxy.net/api/open/app/order/create/v2" \
  -H "Authorization: Bearer $ZTPROXY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "orderType":"dynamic_proxy",
    "poolId":"<productId>",
    "trafficAmount":3,
    "userId":1001,
    "unitPrice":0,
    "totalAmount":0,
    "ipCount":1,
    "duration":30,
    "unit":1,
    "remark":"API rotating order"
  }'

trafficAmount is measured in GB. The server applies the same role-aware price used by the web application; unitPrice and totalAmount are compatibility fields and must not be treated as a client-selected price.

Response and retry rules

• Check both the HTTP status and the response code.
• Treat validation, authentication, permission and insufficient-balance errors as non-retryable until the request or account is corrected.
• Retry timeouts and temporary 5xx responses with exponential backoff and an idempotency key where the endpoint supports one.
• Do not assume an order succeeded until its final status and delivered resources are visible.

For endpoint fields and related operations, continue to the English Core API Reference.