Querying for Orders

requires auth

Query Multiple Orders

Clients can use this endpoint to find information about executed orders, within several different parameters, that can be used alone or in combination.

For instance, client might want to get all orders for BTC/USD executed between 01/01/2023 and 01/12/2023.

GET /api/v1/routing/order/account/{accountId}

Path Parameters:

Path	Type	Description
accountId *	string	your account ID

Query Parameters:

Query	Type	Description
submittedAtStart	string	Initial date and time for the query. ie.: '2022-12-21T22:07:38.6325460Z'
submittedAtEnd	string	end date and time for the query. ie.: '2022-12-22T22:00:00.0000000Z'
destination	string	the asset you want to buy
source	string	the asset you want to sell
type	string	order type (market)
startAtOrdering	string	the order of the order in which to start query. ie.: '1081'. Please note that the order increment value is a global value to 1Konto and not specific to your integration. As such, the value will increment by at least 1.
status	string	status of the ordered (filled, rejected, canceled, invalid, submitted, partially-filled )
max	string	maximum number of orders in the response
asc	boolean	ascending true or false

Example

GET /api/v1/routing/order/account/myAccountId?source=USDT

// Successful Response body
{
    "max": 100,
    "orders": [
        {
            "orderId": "abcd01234",
            "ordering": 1081,
            "accountId": "myAccountId",
            "size": "100 USDT",
            "source": "USDT",
            "destination": "BTC",
            "type": "market",
            "submittedAt": "2023-02-21T22:07:38.6325460Z",
            "result": {
                "status": "filled",
                "price": "0.0000411222366 USDT/BTC",
                "invertedPrice": "24317.74 BTC/USDT", 
                "updatedAt": "2023-02-21T22:07:41.5738620Z",
                "total": "0.00411222366 BTC"
              }
          }
    ],              
    "status": "ok",
    "httpStatusCode": 200
}