Skip to main content

About REST API Response Code Update

Updated
Note: This is a general announcement. The products and services mentioned herein may not be available in your region.
 
Dear Clients,
 
In order to deliver faster API responses and reduce the reliance on checking the code field in the body, we are adding HTTP response codes other than 200.
Estimated launch date: June 5, 2026
 
The code changes involve moving some of the handling of the code field from the original 200 response code logic to the corresponding 400, 401, 403, 404, 429, and 500 response codes.
 
The complete set of REST response codes is shown in the following table:
 
HTTP status code
Description
Code in Body
400
The client should modify the request and retry
  • 10001: JSON syntax error
  • 10004: Invalid Content-Type
  • 11000: Illegal origin
  • 11005-11009: Invalid field / required field missing / parameter error / duplicate request / value out of range
  • 40001-40021: Parameter empty / time range / currency / enumer value – field validation
  • 50001-50032: Trading parameter logic validation (price / quantity / orderType / timeInForce, etc.)
401
API key, signature, or timestamp is invalid
  • 10100-10119: API key frozen / not found / invalid signature / timestamp expired / IP whitelist / account disabled, etc.
  • 11001: Session expired
  • 11010-11012: Signature verification failed / invalid IP / timestamp expired (gateway-level validation)
403
Insufficient permissions or compliance restriction
  • 10120-10128: Account permission prohibits trading / member-level permission / questionnaire incomplete / identity unverified, etc.
  • 11002: No operation permission
  • 13000-13012: IP location restriction / registration region restriction / service not purchased
404
The client requested an invalid endpoint
  • 10003: Interface deprecated or unavailable
429
The client should reduce the request frequency
  • 10005: Request rate too high
  • 10008: Gateway-level rate limiting
  • 11004: Rate limiting
  • 14001: System traffic peak rate limiting
500
This is not a client-side issue; the client may retry directly
  • 10002: Network error
  • 10006: System busy
  • 20001: Service temporarily unavailable
  • 20002: System error
  • 20003: System execution exception
  • 20004: Upstream securities system error
200
 
Insufficient balance, position limit exceeded, etc. – The request itself is valid, but the business state does not allow it
  • 20005-20060: Insufficient balance / order not found / invalid leverage / duplicate request / invalid trading pair, etc.
  • 50100+: Spot does not support leverage / options not supported / MMP group rules / STP and other trading rules
  • 60100+: Available balance insufficient / borrowing limit exceeded / position limit exceeded / price protection / order restrictions, etc.
  • 70100+: WebSocket related

 

Terms and Conditions

The country or region where users reside will affect their eligibility to trade the above new trading pair. Please note that the list of restricted countries may be updated due to mandatory changes in applicable laws and regulations, or due to other changes related to this trading pair. Users must complete account verification to participate in trading this new trading pair.
To use any services provided by our relevant service entities, you must reside in a country or region where the relevant services are available. Depending on your location and other applicable eligibility requirements, some features may not be accessible to you. If you have any questions, please contact us.
 
 
Thank you for your support!
 
XCoin Team
 
May 29, 2026
 
Note: This is a general announcement. The products and services mentioned herein may not be available in your region.

Related articles