Get company funding rounds and investor relationships

View all Crunchbase Company & Investment Data endpoints →

Retrieve funding-round records and a funding summary for the company identified by the required company query parameter. Documented identifier forms are a Crunchbase organization permalink, UUID or full crunchbase.com/organization/ URL. The optional page parameter accepts integers from 1 through 100 and defaults to 1. The optional sort parameter accepts announced, amount or rank and defaults to announced. The documented sorting constraint is important: announced and amount return one page; rank supports deeper paging. More pages do not establish complete financial coverage. The observed Stripe response was an object containing company, count, per_page, current_page, total_pages, next, previous, items and summary. Company identities included id, uuid, name, type, link and image. Round items included id, uuid, name, link, company, round_type, investors_count, lead_investors, investors and rank, along with nullable financial and date fields. Lead-investor identity references included id, uuid, name, type and link. The retrieved records included Series I, H, G and secondary-market rounds. An investor count should not be assumed to equal the number of populated investor identity references in an item. Observed summary fields were total, equity_total, stage, rounds_count, last_round_type, last_round_at, investors_count and lead_investors_count. The Stripe response reported count=24 and summary.rounds_count=24 but returned only 15 items, with current_page=1, total_pages=1 and next=null under the default announced sort. Display reported totals separately from the actual rows fetched; this observed page is partial, not a complete funding history. Every observed round had null amount, target_amount, pre_money_valuation, post_money_valuation, announced_on and closed_on. Other observed item fields included is_equity, company_funding_total, company_diversity_spotlights and short_description, which were null in the inspected example item. Summary financial totals, stage and last-round date were also null. Preserve missing values as unknown; do not infer monetary totals, valuations, dates or a chronological history from round names or sort selection. The sort alternatives and deeper rank paging are documented behaviors, not separately verified by the supplied default-sort probe.

API Features

Round-level financing identities Read each retrieved round's identifiers, name and round_type; the observed Stripe page included Series I, H, G and secondary-market entries.
Lead-investor relationship references Use available lead_investors identities with investors_count and the investors array without assuming all counted investors have populated identity records.
Reported totals beside fetched rows Keep count and summary.rounds_count separate from items length; the observed response reported 24 rounds while returning 15 records.
Sort-aware funding pagination Choose announced, amount or rank with the documented constraint that announced and amount expose one page, while rank supports deeper paging.
Company financing summary fields Read summary round counts, investor counts and last-round type, while allowing totals, stage and last-round date to remain unknown.
Nullable amounts and valuations Preserve missing amounts, target amounts, pre- and post-money valuations and announcement dates; all retrieved Stripe rounds had null values for these fields.

Live API Demo

GET /api/project/crunchbase/company-funding-rounds

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/crunchbase/company-funding-rounds?key=<API_KEY>&company=openai&page=1&sort=announced'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

How do I identify the company whose funding rounds I need?

Supply a Crunchbase organization permalink, company UUID or full crunchbase.com/organization/ URL in the required company parameter. The supplied live funding lookup used the stripe permalink; UUID and URL forms are documented rather than independently tested here.

What does a funding-round result contain?

The observed response contained a company object, pagination fields, an items array and a summary object. Round items included identity fields, round_type, investors_count, lead_investors, investors, rank and nullable date and financial fields. The Stripe page included Series I, H, G and secondary-market rounds.

Why can the reported funding-round count exceed the number of items?

The observed Stripe result had count=24 and summary.rounds_count=24 but only 15 items. It also reported total_pages=1 and next=null under the default announced sort. Keep the reported total distinct from the retrieved row count and label this result as partial.

Which sort order supports deeper funding pagination?

The documented default is announced. Announced and amount return one page; rank supports deeper paging, with page documented from 1 through 100. Only the default-sort first page was live-verified here, so neither rank paging nor any sort choice should be presented as a guarantee of complete history.

Are funding amounts, valuations and announcement dates available?

Those fields exist in the observed round records, but amount, target_amount, pre_money_valuation, post_money_valuation, announced_on and closed_on were null in every retrieved Stripe item. Summary financial totals and the last-round date were also null. Null means unknown, not zero; do not derive a dated financing chronology from these rows.

Does investors_count guarantee a full list of named investors?

No. Investor counts and identity arrays are separate fields. Use populated lead_investors and investors references where available, but do not assume those arrays enumerate every counted participant or that missing references indicate no investment relationship.

Related operations

Guides

View Subscription Plans →