HubSpot Developer Changelog (3)

May 2023 Rollup

Announced: May 30, 2023

May 2023 updates bring updated filtering for blog HubL functions, conditional fields in CMS modules, a new WhatsApp module, updated srcset generation, an updated version of our Calling Extensions SDK, support for custom objects in the new Goals API,...

Changes to fields in the Workflows API

Live: August 10, 2023

We're making some changes to some of the fields used in the Workflows API. Certain optional fields will no longer be included in the response for any workflow and other fields will have static, empty values regardless of how the fields may be set...

New member_email field for contacts used for CMS Membership emails

Live: May 8, 2023

We've added a new member_email property to contacts which dictates where membership emails (password reset, password confirmation, and registration) are sent. The following users should be aware of this new property:

April 2023 Rollup

Live: May 1, 2023

April showers bring new HubSpot powers. Better validation for multi-currency accounts, GraphQL available in more Hubs, new phone property type, improved and consolidated UIs, session timeout control for private content, and import tool improvements.

Asset Marketplace April Rollup - Theme updates required by July 12th, 2023

Announced: April 26, 2023

Modules will be released onto the asset marketplace soon. To prepare, we want to make sure your themes are the best they can be. Read on to review required theme updates, and complete these updates by July 12th, 2023.

Upcoming: Property Validations Rules will be enforced for APIs and Integrations

Live: July 24, 2023

Property Validations allow admins to prevent data quality issues before they start. By setting up property validation rules, admins can control what data can be entered into their system ensuring the entry of clean, reliable, and accurate data.

Upcoming Sunset: Calendar API

Live: July 28, 2023

Note: This post has been updated to reflect an updated sunset date of August 31. The original date for this was July 28. We are sunsetting the Calendar API. Beginning on August 31, the API will no longer function, and data from the marketing...

Amendment to Forms API Submission Validation

Announced: April 17, 2023

Whats Changing? Last year (February 2022), we announced some updates to our form submissions API that would make our customer’s accounts more secure, by requiring all fields be declared on the form definition before we would accept these fields in...

Validation changes to company property - Industry

Live: July 14, 2023

Beginning on July 14th, the industry property on company records will begin correctly validating values when company records are created and updated.

Bug fix: Contact Properties updated to indicate they do not force uniqueness

Live: April 12, 2023

We discovered that it was possible using the API to include hasUniqueValue=true in a Contact property's definition. Currently HubSpot doesn't support unique properties in Contacts. So despite the value showing as true, it was ignored and not...

Upcoming Sunset: JSON Custom Cards

Live: March 31, 2024

Previously, HubSpot released a beta allowing users to utilize private apps and projects to build a custom card with JSON-based components for UI extensibility within the CRM development tools.

Upcoming Change: Email Verification Required for All Marketing Emails

Live: October 26, 2023

Starting October 26th, 2023, any marketing emails, including those manually sent or sent through automation that use a personalization token to populate the "From" address field, will require email verification. If an email address is not verified,...

Changes to the lifecycle stage in forms

Live: December 11, 2023

We're changing how the lifecycle stage for CRM records is handled in forms. Instead of being a form field, the lifecycle stage will be included in the form settings in a new selectedExternalOptions field.

Bugfix: New Validation for Hyphen and Numeric Usage in Association Names

Live: November 9, 2023

Association definition names containing a hyphen (-) or starting with a numeric character cause issues for users querying associations via GraphQL. This problem affects all users who utilize associations with such naming conventions.

Apps & Integrations

CMS

References

Community

App Marketplace New

CMS Asset Marketplace

App Partner Program

Latest Posts