Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Common API Errors

When working with the Intrinio API, most issues can be resolved by examining the HTTP status code and the accompanying error message. This guide explains the most common API errors, what they mean, and how to fix them.

400 Bad Request

What it means

Your request could not be processed because one or more parameters are invalid or missing.

Common causes

  • Required query parameters are missing.
  • Invalid parameter values.
  • Incorrect date formats.
  • Typographical errors in parameter names.
  • Values outside the accepted range.

How to fix it

  • Review the endpoint documentation.
  • Verify all required parameters are included.
  • Check parameter spelling and capitalization.
  • Ensure dates use the expected format (typically YYYY-MM-DD).
  • Validate numeric and boolean values.

401 Unauthorized

What it means

Your request was not authenticated.

Common causes

  • Missing API key.
  • Invalid API key.
  • Expired or revoked credentials.
  • Using an API key where OAuth authentication is required (such as the Intrinio MCP Server).

How to fix it

For the REST API:

  • Verify your API key is included correctly.
  • Confirm you're using the API key associated with your Intrinio account.

For the MCP Server:

  • Do not use your Intrinio API key as a Bearer token.
  • The MCP Server requires OAuth 2.0 authentication.
  • Use your OAuth access token generated during the authentication flow. Official MCP SDKs handle this automatically.

403 Forbidden

What it means

Your account is authenticated, but you are not authorized to access the requested resource.

Common causes

  • Your subscription does not include the requested dataset.
  • Your account lacks access to the endpoint.
  • You have exceeded licensing permissions for the requested data.

How to fix it

  • Verify that your subscription includes the requested dataset.
  • Visit Account → Subscription or Account → Access to review your available data feeds.
  • Use the View API Documentation link from your account to see only the endpoints available to your subscription.

If you need access to additional datasets, contact our Enterprise team using the Request a Consultation form.

404 Not Found

What it means

The requested endpoint or resource could not be found.

Common causes

  • Incorrect endpoint URL.
  • Invalid identifier (ticker, company ID, filing ID, etc.).
  • Resource does not exist.

How to fix it

  • Double-check the endpoint path.
  • Verify identifiers are correct.
  • Confirm the resource exists before requesting it.

405 Method Not Allowed

What it means

The endpoint exists, but the HTTP method is incorrect.

Example

Using:

POST /companies

when the endpoint only supports:

GET /companies

How to fix it

Use the HTTP method specified in the API documentation (GET, POST, PUT, DELETE, etc.).

408 Request Timeout

What it means

The request took too long to complete.

Common causes

  • Network connectivity issues.
  • Very large requests.
  • Temporary internet interruptions.

How to fix it

  • Retry the request.
  • Reduce the size of the request if possible.
  • Verify your network connection.

409 Conflict

What it means

The request conflicts with the current state of the resource.

This error is uncommon but may occur when attempting conflicting operations.

422 Unprocessable Entity

What it means

The request syntax is valid, but one or more parameter values are invalid.

Examples

  • Invalid ticker format.
  • Invalid filter combinations.
  • Unsupported enum values.

How to fix it

Review the endpoint documentation and verify each parameter value.

429 Too Many Requests

What it means

You have exceeded your rate limit.

Common causes

  • Too many API requests in a short period.
  • Bursts of requests exceeding your plan's limits.

How to fix it

  • Reduce request frequency.
  • Implement exponential backoff and retries.
  • Cache responses whenever practical.
  • Monitor your API usage from your Intrinio account.

500 Internal Server Error

What it means

An unexpected error occurred on the Intrinio servers.

How to fix it

  • Retry the request after a short delay.
  • If the error persists, contact Intrinio Support and include:
    • Endpoint
    • Request parameters
    • Timestamp
    • Request ID (if available)

502 Bad Gateway

What it means

A temporary upstream service error occurred.

How to fix it

Retry the request after a brief delay.

503 Service Unavailable

What it means

The service is temporarily unavailable due to maintenance or unusually high traffic.

How to fix it

Wait a few minutes and retry your request.

504 Gateway Timeout

What it means

An upstream service did not respond before the timeout period expired.

How to fix it

Retry the request after a short delay.

Best Practices for Troubleshooting

Before contacting support:

  • Verify your API key or OAuth credentials.
  • Confirm your subscription includes the requested data feed.
  • Double-check endpoint URLs and parameters.
  • Review the endpoint documentation.
  • Retry temporary server-side errors (500, 502, 503, 504) after a brief delay.
  • Implement retry logic with exponential backoff for transient failures.
  • Log request URLs, parameters, HTTP status codes, and response bodies to simplify troubleshooting.

You can also quickly discover the endpoints available to your subscription by navigating to Account → Subscription or Account → Access, selecting a data feed, and clicking View API Documentation. The documentation will automatically filter to the endpoints available for your account.

Still Need Help?

If you're unable to resolve an API error, please contact Intrinio Support and include:

  • The endpoint you called
  • The complete request URL (excluding your API key)
  • The HTTP status code
  • The response body
  • The approximate timestamp of the request
  • Any relevant request IDs or correlation IDs

Providing this information will help our team diagnose and resolve your issue as quickly as possible.