Error codes

Business error responses normally produced by the Open API use HTTP 200. Use the response body code to decide whether to correct parameters, query the current result, or retry a safe read request later. Transport failures may not include any JSON error code listed here. See Response structure.

code	Public meaning	Common scenarios	Recommended action
0	Success	The request succeeded	Process data
300001	Data not found	An account, order, or resource does not exist or is inaccessible; a parent region is unavailable	Verify the identifier and ownership; do not retry repeatedly
300006	Duplicate request	The same request_no was reused within 24 hours	Do not resubmit. Use existing list, balance, or resource-status APIs to determine the result. The original response is not replayed
300184	Insufficient wallet balance	The balance is insufficient for a purchase or renewal	Add funds, then use a new request number for the new operation
300320	The resource price does not exist or does not match the requested specification.	—	—
300323	Region unavailable	The region used for static proxy inventory or a purchase order is not currently available, or the credential region cannot be used	Query regions again and select another value
300324	Inventory query failed	Real-time inventory could not be obtained while creating a purchase order	Query inventory later; contact support if the issue continues
300325	Insufficient inventory	The quantity in a purchase order exceeds current inventory	Reduce the quantity or query inventory again later
300328	Dynamic sub-account removed	A change was requested for a removed account	Use another account
300340	Dynamic traffic balance is not positive	The prerequisite for creating a dynamic sub-account is not met	Purchase dynamic traffic first
300341	Dynamic sub-account limit reached	No additional account can be created	Reuse an existing account or contact support
300358	Sub-account name already exists	The name is already used under the current account	Change sub_account and the request number
300370	Source IP address is not in the access allowlist	The user-level IP allowlist is enabled and the current request source does not match an entry	Open the web console, verify the public egress IPv4 address, and configure the IP access allowlist; after a change, wait up to 30 seconds before retrying
400001	Authentication failed	The API key is missing, invalid, or unavailable	Check the production API key and Base URL; do not retry blindly
400009	Invalid request parameters	A field is missing, malformed, unknown, or the HTTP method is unsupported	Correct the request and retry
500000	System processing failed	The request did not complete and the exact cause is not public	Do not assume another request will solve the issue; for creation requests, query the result first

Handling principles

• If a creation request times out or returns 500000, do not blindly resubmit it with either the original request_no or a new one. First follow Request numbers and duplicate submissions to determine the result.
• 500000 does not indicate how long the problem will last and does not guarantee that a repeated request will succeed. Save X-TRACE-ID and contact support if the problem continues.
• 400001, 400009, and explicit business errors usually require the underlying condition to be corrected. Repeating the same request immediately is not useful.