Troubleshooting

📄️ Authentication

Authentication issues usually arise due to incorrect headers, omission of the authorization header, or problems with URL parameters. If you encounter a 401 error, it's usually related to issues with your Authorization header. The most common issues are:

📄️ HTTP Status Codes

The Market Data API uses standard HTTP status codes to respond to each request. By preparing your application to utilize these status codes, you can often times solve common errors, or retry failed requests.

📄️ Logging

Why Logging is Important

📄️ URL Parameters

Introduction to URL Parameters

📄️ Multiple IP Addresses

If your account is blocked, you do not need to contact support. The block will automatically resolve after 5 minutes if you stop making API requests. Simply wait 5 minutes without making any requests from the blocked IP address, then resume with a single device or IP address.

📄️ Service Outages

Market Data, as stated in our terms of service, makes no representation as to the reliability, availability, or timeliness of our service. This is not just a standard disclaimer. We have not yet been able to achieve 99.9% reliability, which is a metric we consider a minimum level of reliability that is needed to operate without a backup provider.

📄️ Running Out of Credits

You've run out of credits or are running low, and you're probably confused about why. The most common reason is a misunderstanding about how credits work: 1 request does not always equal 1 credit. This guide will help you understand what happened, why it happened, and what you can do about it.

📄️ Real-Time Data Not Working

If you're expecting real-time data but receiving delayed or historical data instead, this guide will help you diagnose and fix the issue. The API doesn't throw errors when you're missing required agreements or profile information—instead, it silently provides you with the freshest data you're entitled to receive.