DXtrade Push Ping
The 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.
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.
This is a message of the DXtrade Push API, not an HTTP endpoint. It has no method and no path: it is sent as JSON or XML over an open WebSocket connection.
The message
- Name
- Ping
- Direction
- Request, sent by the client
- Carried by
- WebSocket. The specification describes two WebSocket resources, one for business events and one, ending /md, for market data. The specification writes the address with a placeholder for the host, which each broker or firm that offers DXtrade supplies. Two optional query string arguments are set when connecting: format, XML or JSON, and compression, which can only be gzip.
- Answered by
- Not recorded
Fields
| Name | Type | Description |
|---|---|---|
| typerequired | String | Always Ping. |
| timestamprequired | Timestamp | When the message was sent, in UTC. |
| sessionrequired | String | The token of the session the message belongs to. It comes from the token login of the DXtrade REST API. |
Sample
Written by this site from the fields recorded on this page. It has not been run against a terminal, a server or an account, and the values in it are placeholders. No credential is typed into it: where a field holds one, the placeholder says where it comes from. Nothing is entered on this site.
{
"type": "Ping",
"session": "<the session token from the REST login, from your own environment>",
"timestamp": "2026-10-12T09:00:00.000Z"
}