# API Details

# Identifying Markets

We use a proprietary code to identify all markets and trading venues in our system. This code is called a Financial Identifier, or FinID.

To obtain the FinId, use the list markets endpoint to enumerate all markets you have access to as part of your subscription. You can then use the market details endpoint to see specifics about which securities are included in a FinID.

The FinID is more specific than the standard Market Identifier Code, or MIC. However, you can use the MIC in place of the FinID, and our system will generate the best match. If you need help mapping securities and FinIDs, our team is available to help.

Use the query string parameter fin_id to specify a market or markets. Some endpoints support multiple FinIDs in a single request. To specify multiple FinIDs, separate them by a comma. Whenever possible, we recommend making bulk requests with multiple FinIDs to avoid hitting rate limit restrictions.

# Examples

Remember to use your authentication token for all requests.



Our system does have rate limit restrictions. Specify multiple FinIDs or MICs in a single request to avoid hitting restrictions.

# Formats

Our API supports JSON format and CSV format for most requests. By default, if left unspecified, the response format is JSON.

To get a response in CSV format, use the query string parameter format to specify the output format.


Not all endpoints will support returning the data in CSV format. Please see the documentation on individual endpoints for details on which formats are supported.

# Rate Limits

Our API has rate limits to ensure system resources are available for all customers. If you exceed the rate limit, you will receive an error message 419: Too many requests.

The rate limit is not intended to restrict access. Rate limits can be increased in some cases for Enterprise customers.


You can always check the X-RateLimit-Limit and X-RateLimit-Remaining response headers to see how many requests you have left.

There are several ways to avoid exceeding the rate limit.

# Caching

Response caching should be used to avoid sending the same API call within short period of time. It is particularly important to cache the response from the Market Status API.

# Delays Between Requests

By adding a small 1 second delay between requests you can avoid exceeding the rate limit in most cases.

# Bulk Requests

To avoid exceeding the rate limit, use bulk API requests whenever possible. To send bulk API requests, specify multiple FinIDs in a single request.


Enterprise customers can download all data at once using the Data Download API endpoint.

# CORS Policy

The TradingHours.com API does not support Cross Origin Request Sharing (CORS). This means you cannot send a request to our API from the front-end Javascript of a website. We do not allow this because it would reveal your API key to everyone using your website.

If you see an error saying your request "has been blocked by CORS policy" or there is "no 'Access-Control-Allow-Origin' header is present" then this is the problem.

Instead of sending the request from your websites Javascript, you should send the API request from your back-end server.

Learn more about Cross Origin Request Sharing.