Skip to main content Skip to footer

HubSpot Developer Changelog

Marketing Email API: v3 released to general availability and upcoming sunset for v1

Note: The sunset for the v1 Marketing Email API has been delayed to November 1st, 2025. The post has been updated to reflect the new date.

Today we're announcing changes for the two versions of the Marketing Emails API. 

First, we're releasing the v3 API into stable general availability.

Second, we're announcing the upcoming sunset of the v1 API that will be happening on November 1, 2025.

 

What's changing?

The v3 Marketing Email API was released into beta some time ago and has had few changes since the initial public release. With the release of this API into general availability, the API is now considered stable, and will be subject to our guidelines on breaking changes for any future updates. 

With the release of v3 into stable, we're also announcing the sunset of the legacy v1 version of this API. This sunset will affect the marketing email API endpoints beginning with the url /marketing-emails/v1/.

No changes are being made for other legacy email APIs, and these other APIs, including the legacy email analytics API, will continue to function.

 

Why is the v1 API being sunset?

The v1 API is no longer being updated, and is missing some newer features that have been added to emails.

With the release of support for new ILS lists for the v3 API, the newer v3 API supports the newer API design along with supporting other features of the updated CRM APIs. The v3 API also includes the ability to directly publish or send emails if you have a Marketing Hub Enterprise account or the transactional email add-on.

 

When is this happening?

The v3 API is already available and can be viewed in our developer documentation.

The v1 Marketing Email API will be sunset on November 1, 2025. If you are currently using the v1 API, you will need to migrate your integration to the updated v3 API. Any requests to the v1 API after this date will result in an error.

Please let us know if you have any questions by joining the discussion in our community.