Broker API HubMenu

HTTP status code

HTTP status code: 415 Unsupported Media Type

As text you can copy

415 Unsupported Media Type
Kind
Status code
Read from
RFC 9110, HTTP Semantics, section 15.5.16

What does 415 Unsupported Media Type mean in HTTP?

The server refuses the request because its content is in a format that this method on this resource does not support. The fault may lie in the Content-Type, the Content-Encoding or the data itself.

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

Usually the body was sent without the Content-Type the API expects, or as form data when the API expects JSON. Some HTTP libraries choose the content type from the way the body was passed to them.

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 415 Unsupported Media Type?

Set the Content-Type header to the one the API documents and send the body in that format.

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.