EXECX Order Manager API (1.0.14)

This is the documentation for the EXECX crypto execution platform, it provides a single API to send orders to some of the largest exchanges. In addition to sending orders it can also be configured to actively place orders using the position manager, this allows users to set target positions that will be entered over time using post only orders eliminating taker fees.

EXECX is run locally on your production machines through a Docker deployment, this is done to keep the latency between your trading application and the exchange as low as possible. An API key is required and will be sent you to upon signing up for an EXECX account.

To run EXECX use the following command, we recommend using host networking to reduce latency

$ docker run --net=host --name=execx -d execx/order-manager:latest --key [API_KEY]

An API key is required to verify the subscription and will be checked at start up, you will receive this API key via email when registering for an account.

The following command line arguments are available -

Please follow these notes to get the best performance from EXECX. If latency is a concern then you should focus on finding a machine that is a close as physically possible to the exchange matching engine; this can be achieved by spinning up multiple machines in the correct cloud zone and measuring latency between yourself and the exchange. We recommend using delete orders to ensure you are hitting the matching engine, ping is not enough.

Binance servers are located in AWS Tokyo zone A. Internally EXECX uses the REST order entry API to send orders and the websocket to receive order updates.

OKX servers are located in Alibaba Hong Kong zone C, if you are not able to use Alibaba cloud you can access through AWS and it is recommended to set the REST URL to https://aws.okx.com and the websocket URL to wss://wsaws.okx.com:8443. See here for more information.

OKX does not support pull by symbol except for options, to handle this EXECX internally constructs a batch cancel message for all working orders. This is continuously updated as orders are cancelled or removed to reduce latency on pulls.

Bybit servers are located in AWS Singapore in zone ID apse1-az3.

Deribit does not run their servers in a cloud instead it operates in a data centre Equinix LD4 in Slough, UK. The fastest connection possible is through renting a colocated server in this datacentre. If choosing to run your trading strategy in the cloud then please use a data centre that is as close as possible to Slough, UK.

Internally EXECX uses the FIX protocol for Deribit trading, this should provide a lower latency over the alternative APIs.

Please find an explanation of the features provided by EXECX.

Prior to order entry you must establish a new order session, this is described in the API documentation below. The order session is named allowing you to have multiple order sessions to a single exchange.

All order types are supported, for example market orders will trade immediately at the current top of book price where as limit orders can be placed at specific price and volume points.

If you do not wish to manually create orders you can use the position manager, this service will actively seek to trade into a position using maker only orders, this reduces your total fee cost but increases the time it takes to enter a position. Orders are automatically updated on a time interval to be at the top of book, if the spread allows it will attempt to dime the market to ensure your orders are executed first.

The position manager will iceberg orders based on the minOrderQty configuration, over time these orders will reach your target position. Additionally the position manager can layer multiple levels of icebergs to take advantage of favourable price swings.

To reduce latency between market price changes and orders being sent you can use the trigger manager, this allows setting of groups of orders to be executed whenever a price level is traded. The trigger manager supports directional triggers, for example if a sell order is the aggressor then the up triggers will be activated. For buy side aggressors the direction is down.

The trigger orders are sent to the same exchange as the trigger, this means that it's possible to execute trades on different symbols to the trigger symbol.

NOTE Having a large number of active triggers will reduce performance and increase latency between trade events and orders being sent.

Prometheus metrics are available through the /metrics endpoint. This includes order counts and latencies as well as information from the position manager such as target position and current position.

The metrics use the namespace om.

Order manager API for executing orders on an exchange, provides a websocket for receiving streaming order updates

Websocket API endpoints

Position manager API for entering or exiting positions using maker orders to reduce fees, requires an existing order manager

Trigger manager API allows you to send groups of orders on trade price events, orders can be sent seperately for buy and sell events. Order updates should be consumed through the /subscribeUpdates endpoint.