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

Which API Endpoints Belong to Each Product?

Intrinio’s API endpoints are organized by the type of data they return, while access is determined by the data products included in your subscription.

This means an endpoint does not always belong exclusively to one product. Some endpoints can be authorized by multiple products, and some products provide access to several related endpoints. Your account permissions determine which endpoints and data sources are available to you.

The Fastest Way to Find Your Product’s Endpoints

The most accurate way to see which endpoints are included with a specific product is through your Intrinio account:

  1. Log in to your Intrinio account.
  2. Navigate to Account → Subscription or Account → Access.
  3. Select the data feed or product you want to explore.
  4. Click View API Documentation.

The API documentation will open with the endpoint list automatically filtered for that product.

You can then use the toggle at the top of the documentation to switch between:

  • My Endpoints, which displays endpoints available through your current subscription.
  • All Endpoints, which displays the broader Intrinio API catalog.

Starting from the data feed in your account is generally the easiest approach because the documentation is already filtered to the appropriate product and account access.

Use the Intrinio MCP Server

You can also use the Intrinio Financial Data MCP server to find the right datasets, endpoints, and tools using natural-language questions.

Unlike a static endpoint list, the MCP server is aware of your current Intrinio subscription. It can recommend resources you already have access to and help you avoid building against unavailable feeds or endpoints.

For example, you can ask:

  • “Which endpoints can I use for historical stock prices?”
  • “What tools are available for company fundamentals?”
  • “Which endpoint returns real-time options Greeks?”
  • “Do I have access to ETF holdings?”
  • “What is the best call sequence for standardized financial statements?”

Learn more at:

https://intrinio.com/mcp

Common Product and Endpoint Relationships

The following examples show how major Intrinio products generally relate to API endpoint groups. These examples are not intended to replace the subscription-aware endpoint list in your account.

US Fundamentals

US Fundamentals supports endpoints related to:

  • Companies and company reference data
  • Standardized financial statements
  • As-reported financial statements
  • Fundamentals and data tags
  • Financial ratios and calculated metrics
  • SEC filings
  • Institutional ownership
  • Insider transactions
  • Shares outstanding
  • Company historical data

Common operations include retrieving a company, listing its available fundamentals, obtaining a standardized or as-reported statement, and requesting historical values for a financial data tag.

US End-of-Day and Historical Stock Prices

Historical equities products support endpoints related to:

  • Daily, weekly, and monthly stock prices
  • Adjusted and unadjusted OHLCV data
  • Exchange-level end-of-day prices
  • Dividends
  • Stock splits
  • Price-adjustment factors
  • Historical security identifiers

These endpoints are commonly used for charting, backtesting, total-return calculations, and maintaining historical price databases.

EquitiesEdge

EquitiesEdge provides Intrinio-derived real-time equity values through REST and WebSocket delivery.

Related endpoint groups may include:

  • Real-time security prices
  • Real-time security quotes
  • Exchange-level real-time prices
  • Market movers
  • Intraday intervals
  • Security snapshots
  • Market status

EquitiesEdge is derived data rather than raw exchange-sourced market data. The exact source and permissions available through an endpoint depend on your subscription.

OptionsEdge

OptionsEdge provides Intrinio-derived real-time options values and analytics.

Related endpoint groups may include:

  • Real-time options prices
  • Options Greeks
  • Implied volatility
  • Real-time option chains
  • Prices by underlying ticker
  • Prices by strike
  • Options statistics
  • Implied move calculations
  • Options snapshots
  • WebSocket streaming

Some options endpoints can also operate with delayed or exchange-sourced options products. The endpoint may be shared, while a request parameter, data source, or account entitlement determines which product supplies the response.

End-of-Day and Historical Options

Historical options products support endpoints related to:

  • End-of-day option prices
  • Historical option chains
  • Bid and ask values
  • Volume
  • Open interest
  • Implied volatility
  • Historical Greeks
  • Option expirations and contracts

These endpoints are typically used for options research, backtesting, volatility studies, and historical chain analysis.

Delayed Options Data

Delayed options products can support endpoints related to:

  • Delayed quotes
  • Option chains
  • Trades and quotes
  • Interval data
  • Unusual options activity
  • WebSocket streaming

A real-time, delayed, derived, or historical product may use a similar endpoint family. Your entitlement and the endpoint’s source parameters determine which version of the data is returned.

Tick-Level Market Data

Tick-level market-data products support endpoints and delivery methods related to:

  • Individual equity trades
  • Quotes
  • Bid and ask updates
  • Trade and quote condition codes
  • Exchange identifiers
  • Microsecond timestamps
  • Historical replay files
  • WebSocket streams

Because tick data can generate a high volume of events, developers should also review connection limits, subscription limits, throughput, and storage requirements.

Security Master Data

Security master products support endpoints and bulk files related to:

  • Securities
  • Companies
  • Exchanges
  • Listing status
  • FIGI and other identifiers
  • Share classes
  • Security histories
  • Company-to-security relationships

Reference endpoints are often shared with other products because many financial-data responses require company, security, or exchange identifiers.

Bulk Downloads

Bulk-download access is exposed through the bulk-download links endpoint. The files returned are based on the bulk products enabled for the authenticated account.

Because bulk availability is account-specific, the endpoint returns only active downloads associated with your subscription.

Why One Endpoint May Belong to Multiple Products

An API endpoint describes an operation, such as retrieving a security quote or an options chain. A product describes the underlying dataset and access rights.

For example, an options-chain endpoint may support:

  • Historical end-of-day options
  • Delayed options data
  • Derived real-time options data
  • Raw exchange-sourced real-time options data

The endpoint remains similar, but the available source, response freshness, licensing requirements, and account authorization can differ.

Intrinio’s endpoint metadata connects API operations with their related data feeds and access codes. The API currently contains hundreds of operations and data feeds, so a static one-product-to-one-endpoint list would quickly become incomplete.

An Endpoint in the Documentation Is Not Automatically Included

The existence of an endpoint in the API documentation does not mean every account can use it.

Access depends on:

  • Your subscribed plan and products
  • The data feed required by the endpoint
  • The requested data source
  • Exchange or third-party approvals, when applicable
  • Any permissions defined in your order form

Some endpoints may also support more than one authorized data source. When that happens, one account may receive data from a different product than another account using the same endpoint.

Use the OpenAPI Specification for Implementation

After identifying the correct product and endpoint, use Intrinio’s OpenAPI specification as the technical source of truth for:

  • Endpoint paths
  • Operation names
  • Query parameters
  • Required request values
  • Request bodies
  • Response schemas
  • Data types
  • Example structures

The specification can also be loaded into AI coding assistants to reduce invented endpoint names, incorrect parameters, and response-schema errors.

Instructions for accessing it are available here:

https://help.intrinio.com/how-can-i-access-the-open-api-spec

What If I Do Not Have Access?

When you call an endpoint that requires a product your account does not include, the API will generally return an authorization error.

Before changing products, first confirm that the dataset is truly required for your application. In many cases, an included derived, delayed, historical, or bulk alternative may satisfy the use case.

Products included in the Individual and Startup Plan Data Packages cover a broad collection of fundamentals, historical equities, historical options, derived real-time equities and options, delayed options data, tick-level data, and selected bulk downloads. Premium, exchange-sourced, specialty, and custom datasets may require an Enterprise Custom arrangement.

For assistance with data not included in your account, request a consultation:

https://intrinio.com/request-a-consultation#consultation-form

Recommended Workflow

For the most reliable implementation process:

  1. Start from the product listed in your Intrinio account.
  2. Open its filtered API documentation.
  3. Use My Endpoints to confirm access.
  4. Ask the Intrinio MCP server to recommend the best call sequence.
  5. Use the OpenAPI specification for exact parameters and response schemas.
  6. Test the endpoint with your own API credentials.
  7. Review licensing requirements before displaying, redistributing, or commercializing the data.

This workflow helps ensure that your application uses the correct endpoint, data source, subscription entitlement, and implementation pattern.