Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.sacra.com/llms.txt

Use this file to discover all available pages before exploring further.

A company is the core entity in Sacra. Everything else — documents, metrics, events, news, filings — is associated with a company. Each company represents a single operating business, identified primarily by its domain, and carries a profile that includes its description, founding year, headquarters, key people, financials, and Sacra’s original research on it.

​
Coverage universe

Sacra covers growth-stage and pre-IPO technology companies — the roughly 500–1,000 private companies that matter most to investors, analysts, and builders tracking the private markets. This is a deliberate contrast with platforms like PitchBook or Crunchbase, which index 3 million or more companies. Sacra’s value is depth, not breadth: for every company in our coverage universe, we produce original research, revenue estimates, valuation models, and curated news — rather than aggregating whatever public information is available. If you’re building on Sacra, you’re working with a curated set of high-signal companies, not a raw directory.

​
How companies are identified

Sacra uses several identifiers for companies, which appear across API responses:
FieldTypeDescription
domainstringThe company’s primary website domain (e.g. stripe.com). This is the primary identifier used across the Sacra API.
slugstringSacra’s unique short-name identifier for the company (e.g. stripe). Human-readable, URL-safe, and stable.
idintegerSacra’s internal numeric ID. Stable and unique, but prefer domain or slug for readability.
cikstringSEC Central Index Key, where available. Present for companies that have filed with the SEC.
Domain is the recommended way to look up and reference companies. Most API endpoints accept company_domain as a query parameter, and it’s the most portable identifier across integrations.

​
Company entity fields

A full company object from the detail endpoint includes:
  • Identity — id, slug, name, domain, type (private or public), is_active
  • Profile — description, founding_year, headquarters (city and country), logo
  • People — key_people with founders and ceo arrays
  • Structure — legal_entities (name and country of incorporation)
  • Categories — Sacra’s internal taxonomy, each with id, name, and slug
  • Financials — financials array with name/value pairs for revenue, valuation, and funding
  • Listings — exchange listings with venue, ticker, and dates (for companies that have gone public)
  • Milestones — company events (IPOs, acquisitions, etc.) with type, date, and description — see Events
  • Social — links with url and type (twitter, linkedin)
  • Documents — associated Sacra research documents
  • Datasets — revenue and metric time-series data via company_datasets

​
Example

curl -H "Authorization: Token YOUR_API_KEY" \
  "https://sacra.com/api/v1/companies/stripe/"

{
  "company": {
    "id": 1,
    "slug": "stripe",
    "name": "Stripe",
    "domain": "stripe.com",
    "type": "private",
    "is_active": true,
    "cik": null,
    "founding_year": 2010,
    "headquarters": { "city": "San Francisco", "country": "US" },
    "description": "Global payments infrastructure for the internet.",
    "categories": [
      { "id": 4, "name": "Payments", "slug": "payments" }
    ],
    "financials": [
      { "name": "revenue", "value": "..." },
      { "name": "valuation", "value": "..." }
    ],
    "key_people": {
      "founders": [{ "name": "Patrick Collison" }, { "name": "John Collison" }],
      "ceo": [{ "name": "Patrick Collison" }]
    }
  }
}
Use domain when querying the API wherever possible — it’s the most stable and human-readable way to reference a company across endpoints.