Secondary emails with API v3

Smart CRM & Sales Hub CRM
1

Hello,

As Contact API v1 will be deprecated, I need to add secondary email to contacts using API v3, but hs_additional_emails seesm toi be read only.
How can I add/remove/update secondary email using API v3 ?

Regards,
David

2

Hi @dscreve,
Thank you for posting to the Community!
I’d like to tag in some of our Top Contributors to take a look here :slightly_smiling_face:
Hi @mangelet @Gonzalo and @Teun Do you all have any tips on how to add, remove, and update the secondary email using the API v3?
Thank you!
Cassie, Community Manager

3

Hi David,

Yeah this is one of the more frustrating parts of the v1 to v3 migration. The `hs_additional_emails` property is calculated and read only in v3, so you can’t just PATCH it like a regular contac property.

The only documented way to add or update secondary emails programmatically is still through the legacy v1 endpoints, specifically `POST /contacts/v1/secondary-email/{vid}` to add one, and `PATCH` on the same path to update an existing secondary email (Announcement: Secondary Email API now in Developer Preview).
HubSpot announced a Secondary Email API in developer preview a while back but it never really graduated into a stable, fully documented v3 equivalent. At Stacksync we connect to quite a few HubSpot portals and this particular gap comes up more than you’d think, especially for teams that manage contacts with multiple business emails.

My recommendation is to keep using those v1 secondary email endpoints alongside your v3 contact calls for now. The recent v1 sunset announcements (Extension: Contact Lists API (v1) sunset moved to April 30, 2026) are specifically about the Contact Lists API, not necessarily the secondary email endpoints, but I’d still open a support ticket with HubSpot to get clarity on the deprecation timeline for those so you’re not caught off guard later.

Hope this helps David.