Company data

Add company identity, classification, branding, and workforce history to your application. Company routes resolve supported identifiers to a canonical business record while preserving the relationship between primary and secondary exchange listings.

Choose a company endpoint

Select the resource that matches the data or asset you need.

GoalEndpointResponse
Display business and listing detailsRetrieve a company profileOne JSON company profile.
Analyze workforce changesList employee countsA cursor-paginated fiscal-year series.
Render a company markRetrieve a company logoRaw WebP or PNG image bytes.

Resolve a company

Company endpoints accept a company-profile ID (cmp_...), ticker ID (tkr_...), exchange-qualified symbol such as NASDAQ:AAPL, or FIGI. When a user provides ambiguous text, start with ticker search, let the user select a listing, and store its stable public ID for later requests.

A profile always describes the primary listing. Its company_symbols array lists the company's exchange-qualified symbols with the primary listing first. Employee counts are also company-level data, so a secondary listing resolves to the same primary company record.

Combine company resources

Retrieve the profile first when you need the company name, classification, primary symbol, and related listings in one stable shape. Profile fields remain present and use null when a value is unavailable.

Employee results omit fiscal years without a reported figure, so don't treat a gap as zero headcount. Logo responses support WebP and PNG variants, expose an ETag, and accept conditional requests so you can avoid downloading unchanged images.

Common use cases

Use these resources anywhere a security needs company context.

  • Company overview pages. Build profile views with business descriptions, classifications, contact details, reporting dates, and external identifiers in one consistent resource.
  • Cross-listing views. Show one canonical company across several exchange listings while preserving the qualified symbol for each security.
  • Watchlist branding. Add appropriately sized company logos to watchlists and search results, then use conditional requests to avoid downloading unchanged images.
  • Workforce trend analysis. Chart fiscal-year headcount to track workforce changes while keeping omitted reporting years distinct from zero employees.
  • Fundamental research. Combine profiles with statements, ratios, prices, and earnings calls to give each financial resource clear company context.

Caching

Company responses use private cache directives. Cache profile and employee data according to the returned headers. For logos, retain the ETag and send it in If-None-Match to receive 304 Not Modified when the selected variant has not changed.

Next steps

Use these pages to resolve a listing and add company context.