Broker API HubMenu

HTTP status code

HTTP status code: 504 Gateway Timeout

As text you can copy

504 Gateway Timeout
Kind
Status code
Read from
RFC 9110, HTTP Semantics, section 15.6.5

What does 504 Gateway Timeout mean in HTTP?

The server was acting as a gateway or proxy and did not get a timely response from the upstream server it needed in order to complete the request.

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.

Independent and unofficialrfc-editor.orgchecked

What it means in trading API work

The front door gave up waiting. The service behind it may still have received the request and may still act on it. For a request that places, changes or cancels an order, the outcome is unknown, not failed.

This part is this site's own explanation, written for people learning to call a trading API. It is not part of the source cited above and it describes no particular broker.

What should I do about 504 Gateway Timeout?

Treat an order request as unknown: read open orders, positions and recent activity before doing anything else. Retry reads after a pause.

This page is an independent explanation in plain words. The definition itself is in the source it was read from, which is the authority if the two ever differ.