HTTP 409 in broker APIs: what it means, broker by broker
5 decoded error codes from 3 brokers and platforms return this status, and one general record gives the standard's meaning: 6 records on this page. The count is of records whose recorded HTTP status is 409. A search for the number 409 also finds records that only mention it in their code or meaning, so the error lookup can show more.
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.
What the status means in general
HTTP 409 is Conflict. The request could not be completed because it conflicts with the current state of the resource. The standard says this code is for cases where the user might be able to resolve the conflict and resubmit.
Something about the present state of the account or the order clashes with the request: an order already cancelled or filled, a duplicate of a request already received, a change made against a stale version.
Read the present state first, then decide whether the request is still needed. Sending it again without looking risks doing the same thing twice.
The first paragraph is the standard's meaning in this site's words, with its source. The rest is this site's own explanation and describes no particular broker. HTTP 409 Conflict on its own page.
The status alone is only the category. The code or message in the body of the reply is what tells you the cause, and that differs from one API to the next.
The decoded errors that return it
In order of broker name, then code. Each row links to the full meaning and the fix.
DXtrade APIs
| Code | Meaning, first sentence | Source |
|---|---|---|
| 100 Order with this id already exists | DXtrade errorCode 100, description "Order with this id already exists" (the vendor's wording). | demo.dx.tradechecked |
| 409 Conflict | DXtrade REST API: The API understood the request, but it has semantic issues and could not be validated. | demo.dx.tradechecked |
| 1005 Reference order is closed | DXtrade errorCode 1005, description "Reference order is closed" (the vendor's wording). | demo.dx.tradechecked |
eToro
| Code | Meaning, first sentence | Source |
|---|---|---|
| HTTP 409 | The position is closed and cannot be edited, so the change was refused. | api-portal.etoro.comchecked |
Saxo OpenAPI
| Code | Meaning, first sentence | Source |
|---|---|---|
| HTTP 409 (duplicate order) | An identical order was sent within a rolling 15 second window and was rejected. | developer.saxochecked |
Brokers and platforms not listed here have no decoded error recorded with this status. That describes this dataset, not their APIs.