Feb 19, 2020 10:45 AM - edited Feb 20, 2020 2:20 PM
The usage of API keys for the Transactional Email SMTP endpoints listed below is being sunset.
SMTP API Tokens - Password Reset
We’re ending API key usage for these 3 endpoints only starting today unless your account has accessed these endpoints in the past 6 months.
We’ll be contacting all HubSpot accounts that have used API keys to access these particular endpoints only in the last 6 months with more details and a plan for updating their integrations.
This is being done to increase the security, privacy and protection of our email sending platform. Customers must use OAuth to authenticate using these endpoints moving forward.
Wednesday, February 19, 2020
If you have any questions or concerns, please join the discussion here.
Feb 24, 2020 9:47 AM - edited Feb 24, 2020 10:02 AM
One of the main use cases we purchased your transactional add-on for is to act as an SMTP server for our Subscription Billing Tool. That tool's SMTP config allows for us to enter a Server Address, Username, Static Password and Port number. It does not allow for the ability to actively retrieve and refresh tokens as is necessary with OAuth. Is Hubspot's stance that the will no longer support a standard SMTP integration such as this?
Feb 25, 2020 8:28 AM
We're currently investigating this with our Engineers internally and will revert with an update as soon as we can.
Feb 20, 2020 11:33 AM - edited Feb 20, 2020 11:35 AM
If you're going to sunset a feature, it would be really useful to prominently display a timescale by which we are expected to transition to the new method - telling us it's happening but not saying when makes it very difficult to prioritise the dev work required to respond to this 😞
I'm... I'm assuming that API keys didn't actually die yesterday as the only date on your post suggests? Because that's not sunsetting, that's axeing.
Feb 20, 2020 2:25 PM
Feb 21, 2020 3:34 AM
Thanks for clarifying, much appreciated.