Request Process
Online Support avatar
Written by Online Support
Updated over a week ago

The root URL for REST access:


All requests are based on Https protocol, contentType in the request header must be uniformly set as: ‘application/x-www-form-urlencoded’.

Request Process Descriptions

1、Request parameter: parameter encapsulation based on the port request.

2、Submitting request parameter: submit the encapsulated parameter request to the server via POST/GET/PUT/DELETE or other methods.

3、Server response: the server will first perform a security validation, then send back the requested data to the client in JSON format.

4、Data processing: processing server response data.


HTTP status code 200 indicates a successful response and may contain content. If the response contains content, it will appear in the corresponding returned content.

Common Error Code

  • 400 Bad Request – Invalid request format

  • 401 Unauthorized – Invalid API Key

  • 403 Forbidden – You do not have access to the requested resource

  • 404 Not Found

  • 429 Too Many Requests

  • 500 Internal Server Error

We had a problem with our server


All REST requests that return datasets use cursor-based pagination.

Cursor-based pagination allows results to be obtained before and after the current page of the result and is well suited for real-time data. The subsequent requests can specify the direction of the requested data based on the current returned results, before and/or after it. The before and after cursors can be used by the response headers CB-BEFORE and CB-AFTER.

For example:

GET /orders?before=2&limit=30

Did this answer your question?