What is it?

Activity auto-association rules — which control whether an activity logged on one record (e.g., a call on a Contact) is also logged on associated records (e.g., that contact's primary Company) — can now be read and updated via public API.

Why does it matter?

When activities don't flow to the right records automatically, reps lose context and have to manually piece together interaction history across objects. Previously, auto-association rules could only be configured in Settings, and integrators had no programmatic way to read or manage them. With API access, developers and admins can now automate configuration across accounts at scale, making it easier to keep association behavior consistent as your CRM evolves.

How does it work?

Use the following endpoint to read or update auto-association configurations for a specific object type in your account. The {object ID} in the path is the ID of the object type where the activity is being created or logged (e.g., 0-1 for Contacts):

/crm/auto-associations/2027-03-beta/{object ID}

Who gets it?

All hubs and tiers