Enterprise and Applications licensees have access to the full Crunchbase API. Basic Access licensees are limited to the /odm-organizations and /odm-people collection endpoints which return data from the Open Data Map.
The Crunchbase API provides Collection endpoints to retrieve the entire set and core properties of many of the important Item types in the Crunchbase Dataset. The Crunchbase API returns 100 items per page.
Node Type | Endpoint |
---|---|
Organizations | /organizations |
Person | /people |
Category | /categories |
Location | /locations |
Further, the Crunchbase API provides Item Detail endpoints to retrieve not only the core properties of each Node but also the details of related Items.
Such endpoints are available for the following Items:
Node Type | Endpoint |
---|---|
Organization | /organizations/:permalink |
Person | /people/:permalink |
Funding Round | /funding_rounds/:uuid |
Acquisition | /acquisitions/:uuid |
IPO | /ipos/:uuid |
Fund | /funds/:uuid |
The Crunchbase API returns 10 items per relationship type. For example, you might get 10 investments. Then you can use the investments endpoint /organizations/:permalink/investments for an entity to get a further 1000 investments per page if you require more.
To narrow your search, you can provide a relationship name as part of the API request:
Organization Relationships
People Relationships
Acquisitions Relationships
IPO Relationships
Funds Relationships
When you query an entity, you’re now able to specify exactly what results you want to see. Previously with v3, you’d see results for all relationships included in your query. Now you can customize your query to pull only the results that you want to see. For example, if you’re only interested in funding rounds and investors of a company, you can specify this in your query to see only those results. To do this, just add the relationships you’d like to see the results for at the end of the query.
Key set pagination will enable you to traverse our dataset faster. If you’re looking to extract all data results from a given endpoint, you will no longer have to paginate through the entire collection using the page number. We now provide pre-populated pagination URLs in your query results so that you can paginate through the collection efficiently as possible. Using page numbers to traverse a set can cause you to miss entities as the set changes while you paginate. Switching to keyset pagination guarantees that you will never miss an entity! As the set changes the keys remain constant so you can rely on the provided URLs never missing a beat.
In your query results, under the ‘data’ array, there will now be the following fields:
For any queries that return more than 100 results and require pagination, the key_set_url will have the compiled version of the respective fast pagination, so if you continuously use the key_set_url for each page of the results, it will traverse through the collection until you reach the end of the results in which case it will return NULL.
For more information, visit the Crunchbase API documentation: https://data.crunchbase.com/v3.1/docs