Clarification Regarding the Contact Lists v1 Sunset

Developer Support APIs & Integrations
1

Hello!

My company’s integration currently uses the endpoint:

GET /contacts/v1/lists/recently_updated/contacts/recent

On the developer changelog post, it specifies that the:

GET /contacts/v1/lists/:list_id/contacts/recent

will be sunset.

Will the “recently_updated” identifier be included in the sunset? We have the v3 migrations on our roadmap, but need to determine if we would need to update this ahead of the other endpoints if it starts responding with 404s.

Any help would be appreciated!

2

Hi @JMedina3
Thank you for reaching out to the Community!
I’d like to invite some community members who are subject matter experts to join this conversation.
@GRajput @Balaji_Mavlers1 @GiantFocal - Would you be able to share any insights on this? Your expertise would be greatly appreciated.
Best,
Victor

3

Hi @JMedina3
Yes, the GET /contacts/v1/lists/recently_updated/contacts/recent endpoint is part of the v1 Contact Lists API, and HubSpot has confirmed that all v1 list endpoints (including recently_updated) are covered by the deprecation. Once the sunset takes effect, this endpoint will start returning 404s.

For migration:

  • If your use case is tied to list membership, the replacement is the Lists v3 API.

  • If you just need “recently updated contacts” overall, HubSpot recommends the CRM v3 Contacts API . You can use the Search endpoint with a filter or sort on hs_lastmodifieddate to replicate the “recently updated” behavior.

    So yes, you’ll want to plan to migrate this endpoint along with your other v1 → v3 updates to avoid disruption.
    Hope this helps!

4

Thanks, Balaji! Just what I needed to know.

5

Hi @JMedina3

There is no direct API available to fetch the most recently added contact in a list. However, this can be achieved using the following workaround:

GET https://api.hubapi.com/crm/v3/lists/{listId}/memberships/join-order

This endpoint returns list memberships in the order contacts were added. By applying the before parameter, results are returned in descending order. You can then select the first record from the response to identify the most recently added contact.

I hope this solution works for you, and @Victor_Becerra Thanks for inviting me to this conversation!

@JMedina3 If this solved the purpose, then please mark this solution as accepted!

Best Regards,

Gaurav