Excpetions and limits

exceptions and limits

We use HTTP error codes to find success or failure. For success , we get HTTP status code like 2XX. API responses with status code like 4XX or 5XX are considered as errors.

We use HTTP error codes to find success or failure. For success , we get HTTP status code like 2XX. API responses with status code like 4XX or 5XX are considered as errors. We have provided a list of common HTTP error codes for help.

Common HTTP error codes

Code Description
400 Missing or bad request parameters or values
401 Unauthenticated rquest
403 Session expired or invalidate. Must relogin
404 Request resource was not found
405 Request method (GET, POST etc.) is not allowed on the requested endpoint
407 unauthenticated request through a proxy
410 The requested resource is gone permanently
411 The content-length field is required to be defined
413 The requested payload is too long
414 The requested URI is too long
429 Too many requests to the API (rate limiting)
431 Request Header field is too large
500 Unexpected error occurred
501 Request method is not supported by the server
502 The OMS is down and APIs are not able to communicate with it
503 The API service is unavailable
504 Gateway has timed out
505 The HTTP version is not supported by the server

API rate limit

end-point rate-limit
price-time chart 10 req/second
Order Placement 20 req/second
Other endpoints 10 req/second

Other Limits

  • There is a limitation of 500 orders per minute and 20 orders per second.
  • For a single user/API Key, the limit is to place 10000 orders/second per day.
  • A single order could be modified only 25 times
Last modified November 11, 2025: RCA added for SIP failure (16439aa)