# DXtrade Push Ping

Independent and unofficial. Not affiliated with or endorsed by any broker or platform named here. Educational only: nothing here is advice, and nothing here recommends a broker or a trade.

This is the markdown version of https://openbrokerapi.com/platforms/dxtrade/messages/ping, written from the same records as that page.

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.

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.

- Message: `Ping`
- Interface: DXtrade Push API
- Group: Session
- Status: verified. Source: [demo.dx.trade](https://demo.dx.trade/developers/#/DXtrade-Push-API?id=ping), checked 2026-10-12.

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. It is in no OpenAPI file on this site and the request builder does not list it.

## 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

- `type` (type String, required): Always Ping.
- `timestamp` (type Timestamp, required): When the message was sent, in UTC.
- `session` (type String, required): 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.

```json
{
  "type": "Ping",
  "session": "<the session token from the REST login, from your own environment>",
  "timestamp": "2026-10-12T09:00:00.000Z"
}
```

## Related DXtrade Push messages: Session

- [PingRequest](https://openbrokerapi.com/platforms/dxtrade/messages/pingrequest): Sent 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.
- [Reject](https://openbrokerapi.com/platforms/dxtrade/messages/reject): Sent 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.

## More on DXtrade

- [All DXtrade messages](https://openbrokerapi.com/platforms/dxtrade/messages): 8 documented here, grouped by what they do.
- [Log in and keep a session: the call at each API](https://openbrokerapi.com/endpoints/session): The same job at every broker and platform API recorded here, HTTP or not.
- [All DXtrade error codes](https://openbrokerapi.com/errors/dxtrade)
- [DXtrade API page](https://openbrokerapi.com/platforms/dxtrade): The full record: access, authentication, limits and the source for each.

## Licence and how to cite

The records behind this page are all rights reserved. This file is the page itself, at its own address, in another format. It is not part of the CC BY 4.0 downloads listed at https://openbrokerapi.com/data. Quote from it with a link to the page.

Cite as: DXtrade Push Ping. Broker API Hub, https://openbrokerapi.com/platforms/dxtrade/messages/ping, newest check 2026-10-12.

Where you rely on a single figure, cite the source and the checked date printed beside it as well. Where this page and a broker's own documentation differ, the documentation wins.