Documentation

The CrunchBase API gives developers access to query the CrunchBase Dataset for both paginated lists of specific types of Items (e.g., Companies) and details about individual Items (e.g., the properties and relationships of a specific Company).

Developers can navigate through the Dataset by retrieving and inspecting individual Items and their relationships. Each detailed Item response includes not only the properties of the Item (e.g., a Company's name, founding date, and profile image) but also a list of all of its relationship types (e.g., "competitors", "current_team").

Collections

The API provides collections endpoints for each of the three primary Item types in the CrunchBase Dataset:

  1. Organizations
  2. People
  3. Products
Each of these endpoints returns a paginated list of all of the Items of that type in the CrunchBase Dataset. The default ordering is by the entity created_at timestamp in descending order. The sort_order can be set by passing a query parameter to the endpoint, as detailed below.

Sort Order

Each collections endpoint may be sorted by the create and update time of the entity. Sort order is specified by appending a query string to the API endpoint URL:
<created_at|updated_at> <asc|desc>
For example,
http://api.crunchbase.com/v/2/organizations?user_key=<user-key>&order=updated_at%20desc

Each collection response includes both a metadata and a data element.

metadata

The former (metadata) describes the hosts where developers can find the web view for the items in the Dataset, the further api endpoints described in the response, and images described in the response

data

The data section of the response contains two sections, paging and items.

paging

The paging section describes how many total items are available in the CrunchBase Dataset and how to paginate through the list of items. To page through the results, append a query parameter to the endpoint URL:
&page=<page-number>

items

The items section is the paginated list of Items in the Dataset for the particular type. Each Item entry has a condensed collection of properties along with the API endpoint at which the developer can retrieve the complete Item details.

Node Details

For a Node detail response (e.g., /company/facebook), relationships are contained within the "relationships" section, and the system returns a condensed detail of up to 8 related Nodes.

For example, the detailed response for Facebook contains the first 8 members of the Current Team in a section entitled "current_team".

Further, each named relationship section contains a paging section. As above, the paging section describes the total number of items of a certain relationship type (e.g., the current team members at Facebook) and the API endpoint at which one can retrieve that paginated list (e.g., /company/facebook/current_team).

A Note About Dates

CrunchBase supports a variable granularity of dates. That means that some dates in the Dataset may only have a year, some may only have a month and day, and others may have a year, month, and day.

To communicate to developers how to interpret dates in the API, we use a value called a "trust_code". The trust_code tells you which parts of a date you can "trust" as having been entered on the front-end. The mapping of codes to valid fields is as follows:

  • 0 : null or invalid date
  • 1 : day
  • 2 : month
  • 3 : day + month
  • 4 : year
  • 5 : year + day
  • 6 : year + month
  • 7 : year + month + day

Third Party CrunchBase API Libraries

Below are some libraries developed by the community to accelerate developing with the CrunchBase API.

CrunchBase includes links to these libraries purely for convenience and neither endorses nor warranties them in any way.