You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When is this change happening?
Starting November 30, 2022, all customers will no longer have access to API Keys and in-turn will no longer be able to use API Keys as an authentication method with HubSpot APIs.
What this means for developers:
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.
an idea for the improvement
Maybe we could drop off support for API keys in the hubspot-ruby gem and use only a static access token in the Authorization HTTP header. We could release a new major version of the hubspot-ruby gem.
The text was updated successfully, but these errors were encountered:
HubSpot announced the sunset of API keys.
https://community.hubspot.com/t5/Developer-Announcements/Upcoming-API-Key-Sunset/m-p/642739
When is this change happening?
Starting November 30, 2022, all customers will no longer have access to API Keys and in-turn will no longer be able to use API Keys as an authentication method with HubSpot APIs.
What this means for developers:
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.
an idea for the improvement
Maybe we could drop off support for API keys in the
hubspot-ruby
gem and use only a static access token in the Authorization HTTP header. We could release a new major version of thehubspot-ruby
gem.The text was updated successfully, but these errors were encountered: