Errors
In this guide we'll talk about what happens when something goes wrong while you work with the API.
Request limits
Your request limit per month depends on the endpoints you are accessing as well as your subscription level. If you go over your limit, we will email you to let you know, and you may be asked to upgrade your subscription.
During the 14-day trial, you are limited to 1,000 requests for all APIs. If you go over this limit, your subscription will start before the trial ends. Please contact support@orats.com if you need a higher limit.
Additionally, you are limited to 1,000 requests per minute for all APIs.
Ticker limit
For endpoints that have a ticker field that accepts multiple tickers, there is a 10 ticker limit to the query. Certain endpoints allow you to add multiple tickers by using comma-delimited format, but if you go over 10 tickers then you will get an error.
Uptime
In the last five years, our API has only been down twice, and both times were due to an AWS outage. Our API relies on several AWS services to operate, and if we ever experience an outage, we will email you with updates.
Status codes
You can tell if your request was successful by checking the status code when receiving an API response. If a response comes back unsuccessful, you can use the error type and error message to figure out what has gone wrong and do some rudimentary debugging (before contacting support).
Here is a list of the different categories of status codes returned by the ORATS API. Use these to understand if a request was successful.
- Name
2xx
- Description
A 2xx status code indicates a successful response.
- Name
4xx
- Description
- A 4xx status code indicates a client error.
- Name
5xx
- Description
- A 5xx status code indicates a server error.