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

How Products Map to Data Feeds

Intrinio organizes financial data using several related concepts: products, data feeds, API endpoints, and account access codes. Understanding how these pieces fit together makes it easier to find the right documentation, confirm what your subscription includes, and choose the correct API or WebSocket connection.

The basic relationship

The simplest way to think about the structure is:

Plan or subscription → Product → Data feed → Endpoint or WebSocket channel

Each layer serves a different purpose.

Products

A product is the customer-facing data capability included in your subscription or Order Form.

Examples include:

  • EquitiesEdge
  • OptionsEdge
  • US Fundamentals and History
  • US End-of-Day and Historical Stock Prices
  • US End-of-Day and Historical Options Data
  • Delayed options data
  • Tick-level market data
  • Security master data

Products describe the type of data you purchased and the business capability it provides.

Data feeds

A data feed is the underlying entitlement that delivers some or all of a product’s data.

A product may map to:

  • One data feed
  • Several related data feeds
  • Different feeds depending on source, delay, history, or delivery method

For example, a real-time options product may use separate feeds for prices, Greeks, trades, intervals, or unusual activity. Historical and real-time versions of similar data are also commonly represented by different feeds.

Data feeds are often identified internally by codes such as:

  • equities_edge
  • opra_derived_realtime
  • opra_eod_history
  • us_fundamentals
  • company_daily_metrics
  • com_sec_master_data

These identifiers may appear in account entitlements, endpoint metadata, API responses, or documentation filters.

API endpoints and WebSocket channels

Endpoints and WebSocket channels are the delivery methods used to retrieve the data.

One data feed can support multiple endpoints. For example, a fundamentals feed may provide access to:

  • Company reference information
  • Standardized financial statements
  • As-reported financial statements
  • Historical company data
  • Financial ratios
  • Insider transactions
  • Institutional ownership

Likewise, an options feed may support endpoints for:

  • Option chains
  • Individual contracts
  • Prices by ticker
  • Greeks
  • Trades
  • Intervals
  • Unusual activity

The existence of an endpoint in the API documentation does not automatically mean that every account can use it. Access depends on the data feeds included in the account’s subscription.

Example product mappings

The following examples illustrate how customer-facing products may relate to underlying feeds and endpoint groups.

EquitiesEdge

Product purpose: Intrinio-derived real-time U.S. equity pricing.

Typical data includes:

  • Last price
  • Open and close
  • Volume
  • Premarket volume
  • Postmarket volume

Delivery methods:

  • REST API
  • WebSocket

Primary feed: equities_edge

The feed can support several security-price endpoints even though the customer sees EquitiesEdge as one product.

OptionsEdge

Product purpose: Intrinio-derived real-time options values and analytics.

Typical data includes:

  • Synthetic option prices
  • Implied volatility
  • Delta
  • Gamma
  • Theta
  • Vega
  • Strike, expiration, and contract type

Delivery methods:

  • REST API
  • WebSocket

OptionsEdge functionality may map to derived options feeds such as opra_derived_realtime, depending on the endpoint and account configuration.

US Fundamentals and History

Product purpose: Company fundamentals, financial statements, ownership data, and related SEC-derived information.

Typical data includes:

  • Standardized financial statements
  • As-reported financial statements
  • Company reference data
  • Metrics and ratios
  • Insider transactions
  • Institutional holdings
  • Annual and quarterly history

Primary feed: us_fundamentals

This product maps to many endpoint families because a single fundamentals entitlement can support company, filing, fundamental, ownership, and historical-data operations.

US End-of-Day and Historical Stock Prices

Product purpose: Historical U.S. equity pricing.

Typical data includes:

  • Open, high, low, and close
  • Adjusted and unadjusted prices
  • Volume
  • Dividends
  • Splits
  • Adjustment factors

Several endpoints may expose this information by security, exchange, or date range.

US End-of-Day and Historical Options Data

Product purpose: Historical options pricing and analytics.

Typical data includes:

  • Closing price
  • Closing bid and ask
  • Volume
  • Open interest
  • Implied volatility
  • Greeks

Relevant feeds may include opra_eod_history, options_eod_delayed, or other options-history entitlements, depending on the subscription.

Tick-Level Market Data

Product purpose: Trade-by-trade and quote-level market history.

Typical data includes:

  • Trade price and size
  • Bid and ask
  • Exchange codes
  • Condition codes
  • High-resolution timestamps

Historical tick data may use separate feeds for CTA A, CTA B, and UTP securities.

Why one product can map to several feeds

A product is designed around a customer use case, while feeds are designed around data sourcing, licensing, timing, and system delivery.

Separate feeds may be required because of differences in:

  • Real-time versus delayed delivery
  • Historical versus current data
  • Raw versus derived values
  • REST versus WebSocket access
  • Exchange or vendor source
  • Display versus internal-use licensing
  • Geographic coverage
  • Data depth or history length

For example, “options data” is not necessarily a single entitlement. Real-time derived options, delayed exchange options, historical end-of-day options, tick-level trades, and unusual activity can each be delivered through different feeds.

How to find the feeds and endpoints available to you

The fastest method is to begin from your Intrinio account.

  1. Sign in to your Intrinio account.
  2. Open Account → Subscription or Account → Access.
  3. Select the product or data feed you want to use.
  4. Click View API Documentation.
  5. Review the documentation filtered to that feed.
  6. Use the documentation toggle to switch between:
    • My Endpoints, which shows endpoints available under your subscription
    • All Endpoints, which shows the full Intrinio API catalog

Starting from the account page helps ensure that you are looking at endpoints connected to your actual entitlements.

Using the Intrinio MCP server

The Intrinio Financial Data MCP server can also help map your goal to the products, feeds, and tools available on your account.

Because the MCP server is aware of your current subscription, it can recommend:

  • Datasets you already have access to
  • Relevant API operations
  • MCP tools for the requested workflow
  • More efficient batching or pagination patterns
  • Alternatives when a requested resource is not included

Learn more at:

https://intrinio.com/mcp

For AI-assisted implementation, you can also load Intrinio’s OpenAPI specification into tools such as Claude, Cursor, or other coding assistants. The OpenAPI specification is the preferred technical reference for endpoint names, parameters, request bodies, and response schemas:

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

Access is controlled by your subscription

Intrinio subscriptions grant access to specified products and data feeds. The associated API endpoints may then be used according to the permissions, limits, and licensing terms of the account.

Some feeds may also require:

  • Exchange approval
  • A third-party vendor agreement
  • Additional display rights
  • Enterprise licensing
  • Custom rate limits
  • Specific redistribution permissions

Your Order Form controls the products, feeds, limits, and rights included in your subscription. Intrinio’s Terms of Service provide the broader rules governing access, display, redistribution, commercialization, and third-party data.

Common questions

Does one product always equal one data feed?

No. Some products map closely to one primary feed, while others combine several feeds or support multiple entitlement codes.

Does one data feed always equal one endpoint?

No. A single data feed may support many endpoints, depending on the available data and delivery methods.

Why can I see an endpoint but receive a 403 response?

A 403 response commonly means that the endpoint requires a data feed or access code that is not enabled for your account.

Confirm that:

  • The relevant product is included in your subscription
  • The endpoint appears under My Endpoints
  • You are using the correct account and API key
  • Any required exchange or vendor approval is complete

Can I purchase an individual endpoint?

Intrinio plans are generally packaged around products and datasets rather than individual API endpoints. Endpoint access follows the feeds included in the applicable plan or Order Form.

How can I confirm the exact mapping for my account?

Use the data-feed links in your account page or ask the Intrinio MCP server which endpoints and tools are available for your intended workflow.

Summary

Products describe the financial-data capability included in your subscription. Data feeds represent the underlying entitlements. API endpoints and WebSocket channels are the methods used to retrieve that data.

When selecting an endpoint, start with the product in your subscription, identify the corresponding feed, and then use the documentation filtered to My Endpoints. This approach helps you avoid unavailable endpoints and choose the most appropriate delivery method for your application.