DXtrade messages
8 documented messages of the DXtrade Push API, grouped by what they do. Each has its fields, what arrives and the source it was read from.
Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders.
These are messages and subscriptions carried by a connection that stays open, not HTTP endpoints: none has a method or a path. For that reason they are in no OpenAPI file on this site and the request builder does not list them. A message that is not listed is not recorded here, which is not evidence that it does not exist.
Account
3 messages
- AccountMetricsSubscriptionRequestSubscribes to the metrics of chosen accounts, or of all, such as profit and loss and margin. Updates are sent periodically at a frequency set on the server, and less often for accounts with no trading activity.
- AccountPortfoliosCloseSubscriptionRequestCloses a portfolio subscription, by the requestId of the request that opened it. The server confirms, and no more portfolio updates are sent for that subscription.
- AccountPortfoliosSubscriptionRequestSubscribes to the portfolios of chosen accounts, or of all. A snapshot comes first, then the whole portfolio is sent again whenever an order is issued, changed or cancelled, a position changes, or a cash balance changes.
Market data
2 messages
- MarketDataCloseSubscriptionRequestCloses a market data subscription, by the requestId of the request that opened it. The server confirms, and no more market data is sent for that subscription.
- MarketDataSubscriptionRequestSubscribes to market data for a list of symbols: quotes, which carry the latest bid and ask, or candles of a chosen width over a period. The server then sends MarketData messages.
Session
3 messages
- PingThe client's answer to a PingRequest from the server. On receiving it the server extends the session token, so a client that only listens still has to send it.
- PingRequestSent by the server from time to time to check the client is still there. The client is expected to answer with Ping, which extends the session. Where no Ping arrives before a timeout, the server closes the session.
- RejectSent by the server when it cannot process a message. It names the rejected request and carries an error code with a description, so the client can correct the request and send it again.