Calling API Endpoints

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? This guide explains how to retrieve your new API key, complete the migration, and update the Crunchbase endpoints you call.

1. Retrieve your new API key
   1. Login to Crunchbase >Go to Account Settings > Integrations > Crunchbase API.
   2. 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.
   1. Direct in-call authentication: Add your new API key to the endpoint URL syntax
   2. Stored authentication method: Update your saved key if using a platform like Postman or an internal integration
3. Test and Confirm Your Migration
   1. Update and test that all the endpoints are working with your new key.
   2. Once validated, notify our team that the new key is in use so we can deprecate your legacy key.

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.

For additional details, refer to the migration guide on Crunchbase's Knowledge Center.