URLs

RFQ API

We are looking at deploying to various regions over the coming months, optimised for each chain to minimise latency. Please let us know what regions or chains you are interested in.

Payloads to the HTTP or Websocket API follow the JSON-RPC 2.0 specification.

{
    "id": 1,
    "jsonrpc": "2.0",
    "method": "aori_...",
    "params": [{
        ...
    }]
}

Orderbook API

HTTP

All HTTP requests follow the JSON-RPC 2.0 specification.

The HTTP endpoint url is as follows:

You'll be POSTing to the / endpoint with the following request body format:

{
    "id": <request_id>,
    "jsonrpc": "2.0",
    "method": <method_name>,
    "params": [{
        ...
    }]
}

WebSockets

You can also connect via the WebSocket endpoint - the payload also follows the JSON-RPC 2.0 specification.

The WebSocket endpoint url is as follows:

Payloads to the WebSocket endpoint with the following payload format:

{
    "id": <request_id>,
    "jsonrpc": "2.0",
    "method": <method_name>,
    "params": [{
        ...
    }]
}

Each method is listed with their respective body format under the Actions section but you can also find them here:

• Testing Connectivity
• Account Queries
• Retrieving Orderbooks
• Making Orders
• Taking Orders
• Cancelling Orders
• Requesting for Quote

Feed

The feed endpoint is a WebSocket endpoint that streams the orderbook updates to the client. The response follows the JSON-RPC 2.0 specification for response payloads.

The feed endpoint url is as follows:

The response payloads follows the following format:

{
    "id": <request_id>,
    "result": ...
}

Taker Service

The taker service is an endpoint that facilitates interactions that a taker may make e.g requesting for a quote, market orders, requesting a swap etc.

The taker service endpoint url is as follows:

You'll be POSTing to the / endpoint with the following request body format:

{
    "id": <request_id>,
    "jsonrpc": "2.0",
    "method": <method_name>,
    "params": [{
        ...
    }]
}