Financial Data API — Documentation

Financial Data API serves a curated, scored universe of US issuers built from public SEC filings. The companies endpoint lists that universe with classification inline, so sector-aware logic resolves without a per-company fan-out. The entity resolver turns a ticker or CIK you already hold into a Financial Data API entity you can use everywhere else.

Company universe

GET /companies lists the curated fundamentals universe (S&P 500 union Nasdaq-100) with sector and industry inline.

Entity resolution

GET /entities/resolve turns a ticker or CIK into the Financial Data API entity id used across the rest of the API.

What data is available

The universe is the constituents of the S&P 500 and the Nasdaq-100, deduplicated into a single scored set of roughly 505 US companies. Membership is defined by carrying a SEC-derived sector, which excludes raw ticker-directory filers. Each row is intentionally lean: identity plus classification, so you get the ticker, CIK, exchange, domicile country, sector, and industry in one call.

Identity

entityId, name, ticker, cik, and primary exchange for each company.

Classification

SEC-derived sector and industry inline. Every universe member carries a sector.

Linkage

Use entityId, ticker, or cik as the lookup for financial statements and entity observations.

The company universe is assembled from public SEC filings. Identity and classification are official-source and redistribution-safe. The /companies feed is part of the public surface.

Coverage totals change as index membership and filings update. Read live breadth from GET /coverage rather than hard-coding the count.

Authentication

Send your key as x-api-key (or Authorization: Bearer) with the data:read scope. See Authentication.

List the scored universe

GET /companies returns the universe, one company per row, with sector and industry inline. It is a standard cursor-paginated list endpoint. Unknown query parameters are rejected with bad_request.

Parameters

Example

curl "https://api.financialdatapi.com/companies?limit=2" \
  -H "x-api-key: $FINANCIALDATA_API_KEY"

import { FinancialDataApiClient } from "@financialdatapi/client";

const client = new FinancialDataApiClient({ apiKey: process.env.FINANCIALDATA_API_KEY! });

// Auto-paginate over every page of the universe.
for await (const company of client.paginate("/companies")) {
  console.log(company.ticker, company.name, company.sector);
}

Response

{
  "data": [
    {
      "entityId": "ent_aapl",
      "name": "Apple Inc.",
      "ticker": "AAPL",
      "cik": "0000320193",
      "exchange": "NASDAQ",
      "country": "USA",
      "sector": "Information Technology",
      "industry": "Technology Hardware, Storage & Peripherals"
    }
  ],
  "meta": {
    "api_version": "v1",
    "pagination": { "limit": 2, "cursor": null, "next_cursor": "...", "has_more": true }
  },
  "requestId": "..."
}

Example values above are illustrative. Pull the live universe from the endpoint.

Response fields

Resolve by ticker or CIK

GET /entities/resolve turns an identifier you already hold into the Financial Data API entity. Pass the value as alias and, optionally, narrow the lookup with alias_type. Narrowing avoids ambiguity when one string could match more than one identifier kind.

Parameters

Example

curl "https://api.financialdatapi.com/entities/resolve?alias=AAPL&alias_type=ticker" \
  -H "x-api-key: $FINANCIALDATA_API_KEY"

import { FinancialDataApiClient } from "@financialdatapi/client";

const client = new FinancialDataApiClient({ apiKey: process.env.FINANCIALDATA_API_KEY! });

// resolveEntity(alias, aliasType?)
const { data: entity } = await client.resolveEntity("AAPL", "ticker");
console.log(entity.id, entity.name);

Response

{
  "data": {
    "id": "ent_aapl",
    "type": "company",
    "name": "Apple Inc.",
    "slug": "aapl",
    "active": true,
    "metadata": {}
  },
  "meta": { "api_version": "v1" },
  "requestId": "..."
}

An unresolved alias returns 404 not_found. Catch it and fall back to listing the universe if you need to confirm membership.

You can often skip resolution. The financials path lookup accepts a ticker or CIK directly, and the entity observation filter resolves a ticker for you. Resolve explicitly when you want to confirm identity before fetching.

Worked example: find, then pull

Find the company in the universe

List /companies (or resolve a ticker) to get the identity and sector, and confirm membership and classification.

Carry the identifier forward

Use entityId, ticker, or cik as the lookup for financial statements and for entity observations.

Trace any value to its filing

Statement and fundamentals values originate from observations. Follow GET /provenance/observations/{id} to the named SEC source and ingestion run.

Notes and caveats

What defines membership

The universe is the S&P 500 and Nasdaq-100 constituents, deduplicated. Membership is defined by carrying a SEC-derived sector, which excludes raw ticker-directory filers.

Coverage breadth

The universe is US issuers only. Use GET /coverage for the current catalog totals and covered categories rather than assuming a fixed count.

Where classification comes from

sector is SEC-derived and present on every member. industry is the finer classification within the sector and may be null.

Financial statements

Pull income, balance-sheet, and cash-flow statements for any company in the universe.

Economic calendar & events

Company filings surface as issuer_filing events in the unified events feed.

Provenance

Trace any value back to its named SEC source and ingestion run.

Get started

Data products

Data infrastructure

Agent access

Resources

Legal

Companies

Company universe

Entity resolution

What data is available

Identity

Classification

Linkage

Authentication

List the scored universe

Parameters

Example

Response fields

Resolve by ticker or CIK

Parameters

Example

Worked example: find, then pull

Notes and caveats

Financial statements

Economic calendar & events

Provenance

Company universe

Entity resolution

​What data is available

Identity

Classification

Linkage

​Authentication

​List the scored universe

​Parameters

​Example

​Response fields

​Resolve by ticker or CIK

​Parameters

​Example

​Worked example: find, then pull

​Notes and caveats

​Related

Financial statements

Economic calendar & events

Provenance

What data is available

Authentication

List the scored universe

Parameters

Example

Response fields

Resolve by ticker or CIK

Parameters

Example

Worked example: find, then pull

Notes and caveats

Related