Search

How to Update API Calls with your New Crunchbase API Key

Article author
Holly Inglis
  • Updated

Crunchbase has made significant improvements to our data offering including broader data coverage, new endpoints, AI-powered predictive company intelligence, and more.

To support these advancements and to ensure ongoing scalability and support, you are required to migrate your Legacy Crunchbase API Key and CSV plan to a new Crunchbase API Key. This update enables access to Crunchbase’s data quality improvements, enhanced ease-of-use, and ultimately a better support experience.

What’s Changed with Key Access?

Crunchbase has moved away from legacy API keys and introduced new packaging tiers based on access to Crunchbase’s proprietary company intelligence. If you’re a legacy customer, your new API key has been provisioned to a package that reflects your current contract and level of access.  

What steps do I need to take?

We’ve aimed to make the migration process simple. You should have received notice from the Crunchbase team outlining the migration details and next steps. To make it easy we’ve provided the below guide to help you complete the API key migration, so you can update your key and the Crunchbase endpoints you call. For additional context, watch the video for a step-by-step overview.  

  1. Retrieve your new API key
    • Login to Crunchbase
    • Go to Account Settings > Integrations > Crunchbase API.
    • You’ll see your updated API package (the package will be reflective of your legacy plan’s access)
    • Click “Show Key” to access your new API key
  2. Update your API Calls
    • Once you have your new API key, replace your old API credentials in the API calls you make to Crunchbase endpoints. This may be done in one of two ways:
    • Direct in-call authentication: Add your new API key to the endpoint URL syntax
    • Stored authentication method: Update your saved key if using a platform like Postman or an internal integration
  1. Note the URL Path Update
    • All requests using the new Crunchbase API key will now include /data/ after the v4 version in the endpoint path.
      • This is the only structural change to the URL format. You can view a full mapping of legacy URLs to their new format here.
  2. Test and Confirm Your Migration
    • After you’ve made and tested the updates:
      • Validate that your endpoints are working with the new key
      • Once confirmed, let our team know—we’ll deprecate your legacy key

Please note: Once your Legacy API key is deprecated, it will no longer be usable. It is important that you test all endpoints you call to avoid disruption.  


Endpoint Mapping Example

To help illustrate the change, here’s a before-and-after example of Crunchbase’s Organizations endpoint URL: 

Legacy:

https://api.crunchbase.com/api/v4/entities/organizations/ 

Current:

https://api.crunchbase.com/v4/data/entities/organizations 

See the below call to our Organizations endpoint below using a JSON syntax, showing where your new API key should be included:


If your new key is functioning as intended with the above call you would receive:

Have additional questions? Please reach out to enterprisesupport@crunchbase.com for assistance.

Was this article helpful?

0 out of 1 found this helpful

Have more questions? Submit a request