Broker Server Error
Last updated 5 August 2026
Broker Server Error
A "broker server error" means your broker's own server returned an error while processing the request. This is on the broker's side, so in most cases a fix has to come from them. First, re-try the order. If it keeps failing, check whether the broker is having an ongoing problem.
Errors
These errors all mean the broker’s server had a problem. They are temporary and come from the broker’s side, not from us:
- Bad Gateway (the broker returns an HTML error page instead of data)
- Parsing Failed … Body snippet:
<html>(the broker returns a web page, not a proper API response) — but see the note below if your account uses a dedicated IP NoHttpResponseException… the broker’s server failed to respond- HTTP Server Error: Unsupported Media Type
- Read timed out / Connection refused / Connection reset
- Internal Error / “Something went wrong, please try after sometime” (the broker’s system failed while processing the request)
- Request failed (the broker’s order system was busy or could not be reached just then)
- Not able to communicate with OMS / Trade API service is unavailable (Kotak Neo — this often shows up right at the market open, when the broker’s order system is under heavy load)
- Service unavailable (503) / server timeout (Finvasia Shoonya — usually during heavy market-open load, or late-night and weekend maintenance windows)
- “Your broker’s servers are temporarily unavailable (error 502 / 503 / 504)” — a newer, plain-language message that names your broker
- “Your broker is not responding correctly right now” — shown when the broker’s system replies without a proper error detail
Newer messages name your broker and ask you to report the problem to the broker’s API support team. That is expected — the problem is on the broker’s side.
If your account uses a dedicated IP, check this first
A “Parsing Failed … <html>” message that mentions 400 Bad request can also come from your account’s dedicated IP rather than from the broker. In that case the request never reached the broker at all, even though the message names your broker.
Two clues point that way:
- Several of your accounts fail at the same moment across different brokers. Brokers do not fail together; something on the path they share does.
- The message mentions a
400 Bad requestweb page.
If that matches, read Dedicated IP gateway error instead. Nothing was sent to the broker, so no order was placed. Newer versions of the software say so directly — the message names your dedicated IP instead of your broker.
What this error means
This error comes from your broker’s server, not from our platform. The order request reached the broker, but the broker’s system could not process it and sent back an error.
These problems do not happen all the time. They come and go, and they clear up once the broker’s server is working normally again. You do not need to change your login id, password, API key or any other credentials for these errors.
Because the problem is on the broker’s side, there is usually little we can change directly. The fix has to happen at the broker.
How to fix it
- Re-try the order. Many broker server errors are temporary. Placing the order again often works.
- Report it to your broker’s API support team. Because the problem is on the broker’s side, they are the ones who can fix it. If the message names your broker and asks you to report the issue, share the exact message and the time it happened with the broker’s API (developer) support team.
- Check for an ongoing broker issue. If re-trying does not help, the broker may be facing a wider problem. Reach out to our support team to confirm whether there is a known issue with that broker.
