Upcoming: Owner IDs and the Engagements API

[Dadams]

Beginning on July 19th, we will be enforcing the values for owner-type properties in the Engagements API.

What's changing?

Currently, the Engagements APIs allow invalid values for the hs_owner_id and hs_attendee_owner_ids fields. These invalid owner IDs can cause issues with other systems that rely on the record owner, such as workflows or CRM views.

We're going to start enforcing the values of these fields to make sure they match with a valid owner ID. Any requests with invalid owner IDs will return a validation error. Please note that these must be owner IDs from the Owners API, which are separate from users.

This will affect any APIs working with engagements, including the v1 Engagements API, and the CRM v3 beta APIs for:

• Calls
• One-to-one Emails
• Meetings
• Notes
• Tasks

If you're populating either the hs_owner_id or hs_attendee_owner_ids fields, you'll need to make sure that you have the current owners from the Owners API when creating or updating any engagement records. While it is possible to leave these fields blank, leaving hs_owner_id blank may cause issues when reporting on sales activities, and may prevent some HubSpot users from viewing the activity, depending on their permission settings.

When is this happening?

The owner fields will start being enforced on July 19th. We recommend validating the Owner IDs you're using as soon as possible to make sure your integration is ready for this change.

Please let us know if you have any questions by replying below.