Errors that belong to no broker
HTTP status codes in trading API work
19 entries decoded. These are the HTTP status codes a trading API most often returns, and the Retry-After header, as the HTTP standard defines them. Each page says what the entry means, what it means in trading API work and what to do next, and links to the place it is defined: RFC 9110, HTTP Semantics.
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.
Status codes
18 entries
400 Bad RequestThe server cannot or will not process the request because it sees a fault on the client's side, such as malformed syntax or invalid message framing.401 UnauthorizedThe request was not applied because it lacks valid authentication credentials for the resource.403 ForbiddenThe server understood the request and refuses to fulfil it.404 Not FoundThe server found nothing current at the address requested, or is not willing to say that something exists there.405 Method Not AllowedThe server knows the method used, but the resource does not support it.406 Not AcceptableThe resource has no representation that fits the content negotiation headers sent in the request, such as Accept, and the server will not supply a default one.408 Request TimeoutThe server did not receive a complete request within the time it was prepared to wait.409 ConflictThe request could not be completed because it conflicts with the current state of the resource.413 Content Too LargeThe server refuses to process the request because its content is larger than the server is willing or able to process.415 Unsupported Media TypeThe server refuses the request because its content is in a format that this method on this resource does not support.422 Unprocessable ContentThe server understands the content type and the syntax of the request content is correct, but it could not process the instructions it contains.426 Upgrade RequiredThe server refuses to perform the request using the current protocol but might do so after the client upgrades to a different one.429 Too Many RequestsThe user has sent too many requests in a given amount of time.500 Internal Server ErrorThe server met an unexpected condition that prevented it from fulfilling the request.501 Not ImplementedThe server does not support the functionality needed to fulfil the request.502 Bad GatewayThe server was acting as a gateway or proxy and received an invalid response from the server behind it.503 Service UnavailableThe server cannot handle the request for now because of a temporary overload or scheduled maintenance, which is likely to ease after some delay.504 Gateway TimeoutThe 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.
Headers
1 entry
In the headers of an HTTP reply.
How to cite this
HTTP status codes in trading API work. Broker API Hub, https://openbrokerapi.com/errors/http, newest check .
Where you rely on a single figure, cite the source and the checked date printed beside it as well.