My Active Orders

This method is used to obtain information on personal active orders. If successful, it returns a list of active orders.

Details

POST https://api.earnbit.com/api/v1/orders

Headers

Name	Type	Description
X-TXC-APIKEY*	STRING	Public API key
X-TXC-PAYLOAD*	STRING	Сonverted Base64 string containing body JSON
X-TXC-SIGNATURE*	STRING	Encrypted HmacSHA512 string containing body JSON with a API secret key

Request Body

Name	Type	Description	Example
market*	STRING	Any public pair	BTC_USDT
offset	STRING	Default: 0	0
limit	STRING	Default: 50	10
request*	STRING	A request path without the domain name	/api/v1/orders
nonce*	NUMERIC	A 13-character number that must always be greater than the nonce of the previous completed request (we suggest generating a nonce as the UNIX timestamp in milliseconds)	1704070810000

CURL Example

curl --location --request POST 'https://api.earnbit.com/api/v1/orders' \
--header 'Content-Type: application/json' \
--header 'X-TXC-APIKEY: 0000000000XXXXXXXXXXXXXXXXX' \
--header 'X-TXC-PAYLOAD: 0000000000XXXXXXXXXXXXXXXXX==' \
--header 'X-TXC-SIGNATURE: 0000000000XXXXXXXXXXXXXXXXX' \
--data-raw '{"request":"/api/v1/orders","market":"BTC_USDT","offset":0,"limit":10,"nonce":1704070810000}'

200: OK Successful

Response Parameters:

Name	Type	Description
id	STRING	Order ID
left	STRING	Available order amount (order is finished = 0)
market	STRING	Pair name
amount	STRING	Order amount (in 1st ticker of the pair)
type	STRING	Order type (limit / market)
price	STRING	Order price
timestamp	NUMERIC	Time of order creation (TimeStamp format)
side	STRING	Order side (buy / sell)
takerFee	STRING	Order taker fee
makerFee	STRING	Order maker fee
dealStock	STRING	Executed order amount (in 1st ticker of the pair)
dealMoney	STRING	Executed order amount (in 2nd ticker of the pair)

{
    "code": 200,
    "success": true,
    "message": "",
    "result": {
        "limit": 10,
        "offset": 0,
        "total": 2,
        "result": [
            {
                "id": 1041010167,
                "left": "0.1",
                "market": "BTC_USDT",
                "amount": "0.1",
                "type": "limit",
                "price": "60000",
                "timestamp": 1727792722.521000,
                "side": "buy",
                "takerFee": "0.000425",
                "makerFee": "0.000425",
                "dealStock": "0",
                "dealMoney": "0"
            },
            ...
        ]
    }
}

400: Bad Request

Response example 1:

{
    "code": 400,
    "success": false,
    "message": "authentication failure",
    "result": []
}

This error occurs in the following cases:

• The request was signed incorrectly.

• Some of the provided parameters are incorrect.

• Provided nonce is incorrect or less than on previous completed request

• The base URL or path is incorrect.

• The API keys are not activated.

Response example 2:

{
    "code": 400,
    "success": false,
    "message": "invalid input",
    "result": []
}

This error occurs in the following cases:

• One or more body params provided incorrectly

• Required body params are not provided

404: Not Found

Response example:

{    
    "timestamp": 1660811292806,
    "status": 404,
    "error": "Not Found",
    "message": "",
    "path": "/api/v1/order/test"
}

This error occurs in the following cases:

• The request was made with undefined data and the service cannot find the data for response.