Skip to main content
The AssociationUpdate event fires whenever an existing association type definition is modified in a sub-account. Changes can include updating labels, adjusting cardinality, or modifying other relationship metadata. Supports contact-to-contact, contact-to-custom object, and custom object-to-custom object relationship types. Use this event to detect model changes and re-validate downstream integrations that depend on this association structure.

​
Payload

FieldTypeDescription
idstringUnique identifier for the association definition
keystringUnique key for this association type (e.g., "custom_objects.buyer_to_property")
firstObjectKeystringObject type key for the first side of the association
secondObjectKeystringObject type key for the second side of the association
firstObjectLabelstringHuman-readable label for the first object’s role in the relationship
secondObjectLabelstringHuman-readable label for the second object’s role in the relationship
associationTypestringWhether the association is "USER_DEFINED" or system-defined
cardinalitystringRelationship cardinality, e.g. "MANY_TO_MANY"
locationIdstringSub-account ID where the association type was updated

​
Example payload

{
  "id": "67ade73d1119d2ac7ad0c475",
  "key": "custom_objects.buyer_to_property",
  "firstObjectKey": "custom_objects.buyer",
  "secondObjectKey": "custom_objects.property",
  "firstObjectLabel": "Interested Buyer",
  "secondObjectLabel": "Property",
  "associationType": "USER_DEFINED",
  "cardinality": "MANY_TO_MANY",
  "locationId": "eHy2cOSZxMQzQ6Yyvl8P"
}
Last modified on March 4, 2026