Hubspot API is currently transitioning its API authentication from API keys to private apps.
From November 30, 2022, you will no longer be able to use HubSpot API keys as an authentication method to access HubSpot APIs. Instead, you'll need to use a private app access token or OAuth to authenticate API calls.
The following is a description of this change as per Hubspot's own web pages:
“Private Apps work much the same as API key integrations would, with the main change being that they use a static access token in the Authorization HTTP header, instead of using the API key in a query parameter to authorize the API request. No other changes should be required aside from updating the authentication method.”
Our native integration at CloudTalk already uses OAuth, so this will not make any difference to your system for the most part. However, where it will make a difference is in Workflow Automations.
In order to ensure that relevant automations continue working as before, CloudTalk clients using a HubSpot API connection in their Workflow Automation API Request will need to make changes. Specifically, you will need to switch from authentication via URL parameter (API key present in URL) and instead use an Authorization Header along with a Value that contains the respective Bearer token.
How do I generate an Access Token to use in Workflow Automation?
A guide to creating a private app in HubSpot and generating the Access Token can be found on Hubspot's pages.
Replacing your authentication method within Workflow Automation:
Navigate to CloudTalk Dashboard → Account → Workflow Automation.
Open scenario using HTTP Request to send data to HubSpot API.
Remove hapikey parameter from endpoint URL.
Add header where Key is “Authorization” and Value is your newly generated HubSpot token.
Before and after examples for reference:
API request towards HS API before migration
API request towards HS API after migration
If you have any further questions, please get in touch with our support team, we are always happy to help!