Protocol

Author profile photo
Team Quickex
August 21, 2025
~1 min read

The Quickex API uses the HTTP/HTTPS protocol and is based on REST principles.

All requests are executed over HTTPS and use the JSON format for both request bodies and responses.
Standard HTTP methods (GET, POST) and status codes are applied (2xx – success, 4xx – client error, 5xx – server error).

Request Example

POST https://quickex.io/api/v1/orders/public/create
Content-Type: application/json

{
  "instrumentFrom": {
    "currencyTitle": "BTC",
    "networkTitle": "BTC"
  },
  "instrumentTo": {
    "currencyTitle": "USDT",
    "networkTitle": "TRC20"
  },
  "destinationAddress": "your_wallet_address",
  "claimedDepositAmount": "0.01"
}

Response Example

{
  "orderId": "123456789",
  "depositAddress": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
  "status": "waiting",
  "createdAt": "2025-08-22T10:15:00Z"
}

Description of Response Fields

  • orderId – unique identifier of the created order.
  • depositAddress – the address to which the deposit must be sent.
  • status – the current order status (waiting, confirmed, completed, refunded, etc.).
  • createdAt – the date and time when the order was created (ISO 8601).
Note: The Quickex API does not use the JSON-RPC format.
Each request is made as a regular HTTP request, and the unique order identifier is returned by the server in the response.
Share this article: