Look Up Company Subsidiaries and Ownership Context
View all Crunchbase Company & Investment Data endpoints →Look up reported subsidiaries and corporate relationship context for a selected Crunchbase organization. The required company query parameter accepts a Crunchbase permalink such as stripe, an organization UUID, or a full Crunchbase organization URL. No ownership-percentage, relationship-depth or pagination parameter is documented. The endpoint description covers subsidiaries, divisions and acquiring-company context; it is not a complete legal-ownership register. The available response evidence is an unverified documented example rather than an observed live response. Its top-level fields are company, subsidiaries, subsidiaries_count, parent and acquired_by. The company object includes id, image, link, name, type and uuid. Each illustrated subsidiaries entry has its own id, an ownership_type label and a nested company identity object with the same identity fields. All illustrated ownership_type values are subsidiary, so a division-specific record format is not demonstrated. Both parent and acquired_by are null in the example. Their populated structures, ownership percentages and effective dates are not established by this evidence. Treat subsidiaries_count as a reported count, not proof of exhaustive coverage. Preserve null relationship fields and confirm significant ownership or acquisition conclusions independently before merging accounts or drawing legal conclusions.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/crunchbase/company-subsidiaries API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/crunchbase/company-subsidiaries?key=<API_KEY>&company=stripe'
Query Result
Use Cases
- Add reported subsidiary identities and ownership labels to a company dossier after confirming the target organization.
- Flag potentially related CRM accounts for human review without automatically merging subsidiary and parent account records.
- Prepare corporate-family research notes that retain unknown parent and acquirer fields instead of inventing missing links.
- Compare a known corporate-structure list with returned subsidiary records to identify relationships needing independent verification.
- Scope follow-up acquisition research from available acquiring-company context without assuming that a null value rules out an acquisition.
Frequently asked questions
Which company identifiers can I use for the subsidiaries lookup?
The required company query parameter accepts a Crunchbase organization permalink, organization UUID or full Crunchbase organization URL. The documented default is stripe. A website domain or free-text organization name is not a documented substitute.
Which subsidiary fields are documented, and were they observed live?
No live response is recorded for this endpoint in the available evidence. The unverified documented example contains company, subsidiaries, subsidiaries_count, parent and acquired_by. Its subsidiaries entries include id, ownership_type and a nested company identity object.
Does this endpoint provide divisions or a complete legal ownership tree?
The endpoint description covers subsidiaries and divisions, but all illustrated records carry the subsidiary ownership_type. The evidence does not demonstrate a division-specific format, ownership percentages, effective dates or complete corporate-tree coverage. Verify legal ownership separately.
What do null parent and acquired_by values mean?
Both fields are null in the documented example, and their populated structures are not demonstrated. A null value should remain unknown or unavailable in your workflow; it is not proof that the organization has no parent or has never been acquired.
Can I control hierarchy depth or page through subsidiary records?
Only the required company parameter is documented. There are no documented depth or pagination controls. Treat subsidiaries_count as a reported count and avoid claiming that the returned records cover every legal entity or division.