Contacts properties label change

Hello
We have an integration where we map the properties returned by the endpoint /crm/v3/properties/contacts
We used to have for the properties “hs_v2_date_entered_{stage_id}” the labels “Date entered '{stage_id} (Lifecycle Stage Pipeline)'”, but now the api sends us “Date entered “{stage_id} (Lifecycle Stage Pipeline)”” for the label.
It causes problems when mapping as the labels differs. I see the properties have been updated the 08 april 2025, has the labels been changed ?
Thanks in advance

Hi there,

Thanks for raising this — you’re not alone in noticing this change.

It appears that HubSpot has recently updated the labels for the hs_v2_date_entered_{stage_id} properties, likely as part of a backend update to Lifecycle Stage Pipelines. The change you’re seeing — from single quotes to double quotes in the property label (e.g.,
Date entered ‘{stage_id}’ ➝ Date entered “{stage_id}”) — does affect integrations that rely on static label mapping.

While the internal name (name) of the property remains the same, the label field is not guaranteed to be static and can change with HubSpot UI updates. Unfortunately, HubSpot does not always version or announce label changes in API responses.

:white_check_mark: Recommended Solutions:

  1. Map by name, not label
    If possible, adjust your integration to use the property’s name (e.g., hs_v2_date_entered_…) as the stable identifier rather than relying on the label, which is intended for display purposes.
  2. Fallback Matching Logic
    If using labels is necessary (e.g., for user-facing mapping), consider implementing a fallback mechanism that handles minor variations in punctuation or quotation formatting.
  3. Reach out to HubSpot Support
    Since this appears to be a change made on April 8, 2025, you can also raise a ticket with HubSpot Support to confirm if this was an intentional change and whether further adjustments are expected.

Let us know if you’d like help adapting your integration — at Market Minds Creative, we’ve worked with many HubSpot API setups and can help make this more resilient.

Hope this helps!