Access Crunchbase Data

Integrate Crunchbase data into your business, perform analysis, and build applications

API v3 Compared to API v3.1

Introducing our new API v3.1!

We recently launched API v3.1 in beta, so you can start making calls and updating scripts to encompass new functionality and changes. We plan to officially launch API v3.1 on 10/6/2017.

Try out the updated endpoint here.

Our new API v3.1 builds upon the current API v3, but has new capabilities incorporated in order to allow you to get the data that you want in the most efficient manner possible. At a high level, enhancements included in v3.1 include:

Accessing the New API & Timeline

API v3.1 will go live late September.

To prepare, a beta version of v3.1 is currently live for your use. During the beta period, you’ll be able to make calls against a working version of v3.1 ahead of the official launch date. This version will have weekly data refreshes during the beta period, and then daily data refreshes the two weeks leading up to v3.1 launch. There will also be a dedicated support team on call to assist with any questions or potential issues.

Once API v3.1 is officially launched, API v3 will still be available for three months, but we will no longer be pushing updated data to it.

New API v3.1 Features

More Refined Searches

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.

https://api.crunchbase.com/v3.1/organizations/facebook?relationships=funding_rounds,investors&user_key=INSERT_KEY_HERE

Batch Search Capabilities

A new batching endpoint will allow you to pass parameters for several query requests in a single HTTP call, and even specify the relationships for each query. Your queries will be processed in parallel and results will be returned sequentially in the original order. Once all requests have been completed, a consolidated response will be passed back to you and the HTTP connection will be closed. To leverage this, you can now call our batch endpoint:

http://api.crunchbase.com/v3.1/batch

Use an array of requests with the following parameters when calling the batch endpoint:

  • entity_type: any available type that has a collection (Organization, Person, Product, FundingRound, Acquisition, Ipo, Fund)
  • entity_uuid: UUID of corresponding entity
  • relationships: An array with the relationships name (string)
{"requests": [
  { "type": "<entity_type>", "uuid": "<entity_uuid>", "relationships": ["<relationship_name>"]}
]
}
{"requests":[
    { "type":"Organization","uuid":"df6628127f970b439d3e12f64f504fbb","relationships": ["investors","funding_rounds"]},
    { "type":"Organization","uuid":"fd80725f53fc70099878aeecf1e9ffbb","relationships": ["news","featured_team"]},
    { "type":"Organization","uuid":"902deab4ec4168ced9dfc0c959578176","relationships": ["investments","funds"]},
    { "type":"Person","uuid":"43b343a7ff56090a63fa5f833e55ea6d","relationships": ["primary_location","jobs","investments"]},
    { "type":"Product","uuid":"1767f73acc385927b66e51d1308d6c9d","relationships": ["owner","websites"]},
    { "type":"FundingRound","uuid":"08c74f1c6f8d9a2b95a095e61e558ccf","relationships": ["investments","investors","funded_organization"]},
    { "type":"Acquisition","uuid":"11cc4a63be13d7d3191c50bd2cd73a71","relationships": ["acquiree","acquirer","news"]},
    { "type":"Ipo","uuid":"bee91e2e4cfb70deb19d42e4bf991848","relationships": ["funded_company","news"]},
    { "type":"Fund","uuid":"a90b8ad0668ab1d2d5b4162277a3e6df","relationships": ["venture_firm","news"]}
    ]
}

Faster Pagination

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:

  • next_page_url
  • prev_page_url
  • key_set_url

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.

Changes to the API

In the next section we list each endpoint with associated changes...

/organizations/<permalink>

Item
Field Name
Changes in v3.1

field

api_url

new field that includes the full URL of the API endpoint

relationship

primary_image

UUID, created_at, and updated_at will all refer to the entity; height, width, and filesize have been deprecated, these fields will always return 'null'

relationship

board_members_and_advisors

only current board members and advisors will be returned

relationship

headquarters

the following fields have been removed: region_code2, country_code2, country_code3, latitude and longitude

relationship

offices

will only return headquarters location, multiple office locations has been deprecated

relationship

products

product data has been deprecated, this field will always return an empty array

relationship

funding_rounds

the investments nodes which appear within relationships will no longer include copies of the funding_round and funding_organization nodes. the investments will contain a new node for partners.

relationship

investments

within relationships we have added two nodes invested_in and partners; invested_in represents the company raising funds and partners represents the people at this organization who are responsible for the funding round

relationship

acquisition

only the acquiree is returned in the response as the acquirer is implied

relationship

competitors

competitor data has been deprecated, this field will always return an empty array

relationship

customers

customer data has been deprecated, this field will always return an empty array

relationship

memberships

membership data has been deprecated, this field will always return an empty array

relationship

members

membership data has been deprecated, this field will always return an empty array

relationship

websites

will only return 4 results: homepage, facebook, twitter, and linkedin; UUID, created_at, and updated_at will all refer to the entity; blogs have been deprecated, these fields will always return 'null'

relationship

images

duplicates primary_images field, support for multiple images has been deprecated

relationship

videos

video data has been deprecated, this field will always return an empty array

/people/<permalink>

Item
Field Name
Changes in v3.1

field

api_url

new field that includes the full URL of the API endpoint

relationship

primary_image

UUID, created_at, and updated_at will all refer to the entity; height, width, and filesize have been deprecated, these fields will always return 'null'

relationship

advisory_roles

only current board members and advisors will be returned

relationship

investments

within relationships we have added two nodes invested_in and partners; invested_in represents the company raising funds and partners represents the people at this organization who are responsible for the funding round

relationship

memberships

membership data has been deprecated, this field will always return an empty array

relationship

websites

will only return 4 results: homepage, facebook, twitter, and linkedin; UUID, created_at, and updated_at will all refer to the entity; blogs have been deprecated, these fields will always return 'null'

relationship

images

duplicates primary_images field, support for multiple images has been deprecated

relationship

videos

video data has been deprecated, this field will always return an empty array

/products

Item
Field Name
Changes in v3.1

collection

product data has been deprecated, this field will always return an empty array

/ipos/<uuid>

Item
Field Name
Changes in v3.1

field

api_url

new field that includes the full URL of the API endpoint

field

shares_sold

shares sold data has been deprecated, this field will always return an empty array

relationship

stock_exchange

UUID, created_at, and updated_at will all refer to the entity

relationship

websites

will only return 4 results: homepage, facebook, twitter, and linkedin; UUID, created_at, and updated_at will all refer to the entity; blogs have been deprecated, these fields will always return 'null'

relationship

images

duplicates primary_images field, support for multiple images has been deprecated

relationship

videos

video data has been deprecated, this field will always return an empty array

/funds/<uuid>

Item
Field Name
Changes in v3.1

relationship

investors

the investors node will contain a list of investors in the fund. today, the investors node always returns an empty array.

relationship

websites

will only return 4 results: homepage, facebook, twitter, and linkedin; UUID, created_at, and updated_at will all refer to the entity; blogs have been deprecated, these fields will always return 'null'

relationship

images

duplicates primary_images field, support for multiple images has been deprecated

relationship

videos

video data has been deprecated, this field will always return an empty array

/funding-rounds/<uuid>

Item
Field Name
Changes in v3.1

relationship

investments

the investments nodes which appear within relationships will no longer include copies of the funding_round and funding_organization nodes. the investments will contain a new node for partners.

relationship

websites

will only return 4 results: homepage, facebook, twitter, and linkedin; UUID, created_at, and updated_at will all refer to the entity; blogs have been deprecated, these fields will always return 'null'

relationship

images

duplicates primary_images field, support for multiple images has been deprecated

relationship

videos

video data has been deprecated, this field will always return an empty array

/acquisitions/<uuid>

Item
Field Name
Changes in v3.1

relationship

images

duplicates primary_images field, support for multiple images has been deprecated

relationship

videos

video data has been deprecated, this field will always return an empty array

/locations

Item
Field Name
Changes in v3.1

field

region_code2

will be 'NULL' unless the location_type is region (previously was always filled)

field

country_code2

will be 'NULL' unless the location_type is country (previously was always filled)

/categories

Item
Field Name
Changes in v3.1

field

organizations_in_category

field has been deprecated and will always return 'NULL'

field

products_in_category

field has been deprecated and will always return 'NULL'

Changes to the CSV Exports

In addition to changes to the REST API, there will be some changes to our CSV exports.

CSV File
Field Name
Changes in v3.1

events.csv

registration_details, start_time, end_time, venue_address, and cost

These fields have been deprecated.

funding_rounds.csv

funding_round_type, funding_round_code, investment_type

funding_round_type and funding_round_code has been deprecated. investment_type is a composite of those two fields.

funds.csv

started_on

started_on data has been deprecated.

has_competitor.csv

all

Competitor data has been deprecated.

has_customer.csv

all

Customer data has been deprecated.

investors.csv

category_list, investor_list, profile_image_url

These fields have been deprecated.

jobs.csv

is_advisor, is_executive, job_type

The job_type field is a replacement for is_advisor and is_executive.

organizations.csv

logo_url, profile_image_url,
roles, aliases, first_funding_on, zip_code

Sizing parameters have been removed from the logo_url. profile_image_url, first_funding_on, zip_code have been deprecated. roles will now describe all roles and entity can fulfill (e.g. {'investor, company, school'}). aliases is now an array data type.

people.csv

logo_url, profile_image_url

Sizing parameters have been removed from the logo_url. profile_image_url has been deprecated.

products.csv

all

Product data has been deprecated and CSV will be removed.

schools.csv

all

School data is now reflected in the organizations.csv and schools.csv will be removed.

API v3 Compared to API v3.1