Company lookup
Resolve company identities and retrieve normalized profile context.
Developer API
Put Capital Almanac data inside your own tools.
Use supported company lookup, search, financial, transaction, investor and market endpoints to add Capital Almanac data to internal or customer-facing applications.
Search
Search across supported entity and document types from one interface.
Financials
Retrieve supported financial series with reporting-period and source context.
Transactions
Query supported financing and M&A records with related participants.
Investors
Connect investor, fund and portfolio relationships where source data is available.
Source metadata
Carry source and freshness information into downstream workflows.
Developer experience
Simple endpoints with source context.
The API is designed to keep identifiers, reporting periods, sources and freshness visible instead of stripping context from financial data.
GET /v1/companies/example-company
{
"name": "Example Company",
"status": "example",
"metrics": { "revenue": 486200000 },
"source": {
"type": "company_filing",
"period": "FY 2025"
}
}Source context
Keep the source trail visible.
Capital Almanac keeps source context, reporting periods, freshness and unavailable-data states visible so researchers can see what supports a record or conclusion.
Source provenance
Keep the provider, document and evidence trail close to the supported fact.
Linked evidence
Open filings, calls, announcements and other source documents from the research view.
Freshness metadata
See reporting period and update context instead of treating every record as equally current.
Connected records
Understand how companies, people, investors and transactions relate to one another.
Capital Almanac
See how Capital Almanac fits your research process.
Tell us what your team researches, which markets matter and where source visibility or workflow integration would save the most time.
Clear answers for serious research.
How Capital Almanac handles source material, unsupported information and the path from a research question to a reviewable answer.
What should developers expect from the Capital Almanac API?
The API is intended for supported company, search, financial, transaction, investor and related research workflows where the necessary source data and permissions are available. Public documentation should be treated as the source of truth for the endpoints, fields, rate behavior and authentication methods that are actually enabled.
Can an API response omit a field?
Yes. A field can be absent or unavailable when the underlying source does not support it, the record is incomplete or the caller lacks the required entitlement. Applications should handle unavailable values explicitly instead of substituting fabricated defaults.
How is market-data freshness represented?
Freshness should be based on metadata supplied or supported by the market-data provider. Delayed observations must be labeled as delayed and should never be described as live simply because they are the newest values available to the interface.