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

[Dadams]

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.

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 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 replying below.

[Dadams]

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

[DaveRostocil]

Hi,

It seems the new v3 api no longer honors the folderId property?  Is that expected? How would I move an email to a folder?

Thanks,

-Dave

[Dadams · Accepted solution]

Hey all,

This sunset only affects the marketing email API endpoints beginning with the url /marketing-emails/v1/emails. There are no changes to other email related APIs at this time, including the email analytics API

The allEmailCampaignIds field has now been added to the v3 API, and should include the same IDs that you would get from the v1 API in the same format of an array of IDs.

[BretThompson]

@Dadams, Does this mean that the "/email/public/v1" endpoints are being sunset as well or are those a differnt set of endpoints?

HubSpot Community - Re: Email Events v1 Replacement - HubSpot Community

[QDeveloper]

The meta description of the announcement page still shows July 14, 2025.

https://developers.hubspot.com/changelog/marketing-email-api-v3-released-to-general-availability-and...

[DAhmadi]

v3 (https://api.hubapi.com/marketing/v3/emails/) doesn't seem to have the following properties available:

allEmailCampaignIds

primaryEmailCampaignId

We use these fields to tie together campaigns/emails and email events. Is there an alternative in v3 that can be used? Thanks.

[mpolak]

Exactly.

Our problem is that the v3 marketing email is missing the allEmailCampaignIds field. In email events v1 API, we can't fetch the events of an email if we don't have the campaignId of that email.

[MGoswick2]

Does this include the v1 of the transactional api endpoint as well?
https://developers.hubspot.com/docs/reference/api/marketing/emails/transactional-emails/v1