Days until the change takes effect: 60 days
Starting April 7th, 2025, HubSpot will introduce enhanced validation rules for non-string property values, including enumeration and multi-value enumeration submitted via the CRMObject APIs. This change aims to improve data integrity and user experience by:
Stricter Validation for Non-String Properties
400
Bad Request error with a VALIDATION_ERROR
category, providing details on the validation issues encountered.Error Message Example:
Backfilling of Existing Non-String Properties
Ensure all data submissions via the CRMObject APIs for non-string properties, including enumeration options and multi-value enumeration properties, strictly adhere to the new validation rule. Developers should review and update any integrations, scripts, or automated processes that submit non-string property values to HubSpot to ensure compliance with the new validation rules.
Lastly, error-handling routines should be implemented or updated to manage responses from the CRMObject APIs that indicate invalid non-string property values due to the enhanced validations.
For example:
400
Bad Request error with a VALIDATION_ERROR
response because it contains leading or trailing whitespace or invisible characters.400
Bad Request error, with the response indicating a VALIDATION_ERROR
. Note: The initial announcement for this change was made on June 6, 2024, and the release was scheduled for January 6, 2025. However, it was extended to April 7, 2025, to accommodate customers, providing 10 months' notice till the change is released.
Questions or comments? Join us in the developer forums for a peer-to-peer discussion.