Skip to main content
  1. Key Security: The API key is bound to all proxy permissions of the account. Leakage may lead to proxy theft and traffic loss. If a leak occurs, reset the key immediately and check the account for abnormal usage records.
  2. Request Rate Limit: A single key is limited to a maximum of 5 interface calls per second. Exceeding this limit will return a 429 status code (too many requests). Pause for 1-2 minutes before calling again to avoid continuously triggering the limit.
  3. Plan Permission Differentiation:
    1. Traffic Plan: Supports all interfaces, including the region filtering parameter.
    2. Unlimited Plan: Calling the region filtering interface will return a 403 permission error; other interfaces can be used normally.
  4. Parameter Format Validation: Parameters such as date, region code, and session duration must be passed strictly in the format shown in the examples. Otherwise, a 400 parameter error will be returned (e.g., sticky session duration exceeding 120 minutes, invalid region code).
  5. Troubleshooting: When a call fails, quickly locate the problem based on the status code:
    • 401: Invalid or expired key. Verify the key or generate a new one.
    • 403: Insufficient permissions (plan expired / Unlimited Plan calling the region filtering interface).
    • 404: Incorrect interface URL. Verify against the official documentation.
    • 500: Server exception. Retry later or contact customer support.