Cancellation of Enhanced Validation for Non-string Properties in HubSpot CRMObjects APIs

Developer Support Developer Announcements
,
1

We previously announced that HubSpot would implement enhanced validations for non-string property values to improve data integrity and user experience by prohibiting leading or trailing whitespace characters, including invisible unicode characters from property values. However, we have paused this update indefinitely due to customer feedback and impact. No breaking change will go into effect on our originally stated date of November 10, 2025.

All non-string properties will continue to work as expected. If you have implemented any code changes to address this breaking change, your code will not be impacted, and should continue to function as normal.

Questions or concerns? Please let us know down below.

2

Hi, we have implemented an form submission using the forms API endpoint: “https://api.hsforms.com/submissions/v3/integration/submit”. Previously trailing or leading whitespaces in options for multiselect fields were no problem. However since yesterday, these are no longer valid and result in errors.

Is there any chance that part of the API has in fact been affected by the change mentioned above (even though it was canceled)?

Thanks, Niels

3

Hello Niels,

Thank you for your response. We are currently investigating this issue. Could you please send me a link to your form, so I can better understand how you’re uisng the multiselect forms?
Best,

Brooke

4

Hi Brooke,
we are using this form

in our sandbox and we have the same one on our production account.
The fields that are multiselect are: *anlass*, *richtung* and *wunsche* .
Kind regards and thanks for looking into this!
Niels

5

Hi Niels,

Would you please send along the your error response?
Best,

Brooke

6

API RESPONSE CODE :: 400
API RESULT :: {
    “status”: “error”,
    “message”: “The request is not valid”,
    “correlationId”: “2b94ad27-cbdc-413a-8702-197a4676b734”,
    “errors”: [
        {
            “message”: “Error in ‘fields.TICKET.anlass’. Invalid option”,
            “errorType”: “INVALID_OPTION”
        },
        {
            “message”: “Error in ‘fields.TICKET.wunsche’. Invalid option”,
            “errorType”: “INVALID_OPTION”
        },
        {
            “message”: “Error in ‘fields.TICKET.richtung’. Invalid option”,
            “errorType”: “INVALID_OPTION”
        }
    ]
}

7

Hello Niels,

Thank you for this information. I have discussed with the Engineering team regarding this and we have identified the issue. This was a bug related to the multi-select field that has been resolved.
If you’re not subscribed to our Changelog, please do so at HubSpot Developer Changelog to recieve emails directly to your inbox.

Best,

Brooke