On July 9th, 2025, we will introduce two updates to the Campaigns Public API. These updates include all modification endpoints for the Campaigns API—including create, update, delete, and asset management, and any new API endpoints introduced in the future will now require marketing. campaigns.write scope group, while read-only endpoints will continue to require marketing.campaigns.read. Additionally, the deprecated hs_goal property is being fully removed from API responses; although requests referencing it won’t break, developers should ensure their systems no longer rely on this field to avoid null value issues or parsing errors.

For more information about the changes mentioned above, please refer to the details below.

What's changing?

New Scope Group

Today, we’re introducing a permission improvement for the Campaigns Public API. All operations, whether reading or modifying campaigns, now require the marketing.campaigns.write scope group. Specific permission changes include the following: 

• Read-only endpoints will continue to require the marketing.campaigns.read scope group.
• Modification endpoints (e.g., create, update, delete) will require the marketing.campaigns.write scope group.

This scope change applies to newly introduced API endpoints (Marketing Campaign Budget and Marketing Campaign Spend endpoints scheduled to be released soon) as well as existing modification endpoints for the Campaigns API, such as: 

• POST /campaigns
• DELETE /campaigns/{campaignGuid} 
• PATCH /campaigns/{campaignGuid} 
• BATCH endpoints: 
  • POST /campaigns/batch/create
  • POST /campaigns/batch/archive
  • POST /campaigns/batch/update
• Asset endpoints: 
  • PUT /campaigns/{campaignGuid}/assets/{assetType}/{assetId}
  • DELETE /campaigns/{campaignGuid}/assets/{assetType}/{assetId}

Important Note for Developers: If your integration is currently executing campaign modifications using only the marketing.campaigns.read scope group, those API calls will fail once this change takes effect unless the integration also requests the marketing.campaigns.write scope group for the applicable API endpoints mentioned above. This change is being introduced due to an implementation misconfiguration.

Deprecating the hs_goal Property

The hs_goal property has been deprecated and will no longer return values in the response from the Campaigns API. This property has been deprecated in the HubSpot app for some time and is no longer visible or editable within the HubSpot UI. As a result, it's also being phased out of API responses. 

Important Note for Developers: If your integration is still sending or expecting hs_goal, it won’t break the request itself, and HubSpot will silently ignore it. However, if your integration relies on the returned value from hs_goal, this change could cause breakages (e.g., parsing errors or null value handling issues). Make sure your code does not depend on hs_goal values being present in API responses, and remove any logic or mapping tied to this field if it's no longer needed.

When is it happening?

These changes take effect on July 9th, 2025. 

Questions or comments? Join us in the developer forums for a peer-to-peer discussion.