# DXtrade Push Reject

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/reject, 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.

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.

- Message: `Reject`
- Interface: DXtrade Push API
- Group: Session
- Status: verified. Source: [demo.dx.trade](https://demo.dx.trade/developers/#/DXtrade-Push-API?id=reject), 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.

Note: The specification lists two errors any request can bring: code 1, Authorization required, where the session token is missing, invalid or expired, and code 32, Incorrect request parameters, for a malformed request. It says the wording of a description can change without a new API version.

## The message

- Name: `Reject`
- Direction: Event, sent by the server
- 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.

## Fields

- `type` (type String, required): Always Reject.
- `inReplyTo` (type String, required): The requestId of the message that was rejected.
- `timestamp` (type Timestamp, required): When the message was sent, in UTC.
- `payload` (type error object, required): The error, with the two fields below.
- `payload.errorCode` (type not stated, required or not: not stated): The error code. Each distinct error has its own.
- `payload.description` (type not stated, required or not: not stated): A description of the problem, in English.

## Related DXtrade Push messages: Session

- [Ping](https://openbrokerapi.com/platforms/dxtrade/messages/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.
- [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.

## More on DXtrade

- [All DXtrade messages](https://openbrokerapi.com/platforms/dxtrade/messages): 8 documented here, grouped by what they do.
- [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 Reject. Broker API Hub, https://openbrokerapi.com/platforms/dxtrade/messages/reject, 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.