Association type ids between a custom object and a standard object (and the custom object's own type id) differ by portal; read them with GET /crm/v4/associations/{fromObjectType}/{toObjectType}/labels instead of hard-coding them.
Measured
More facts from this area
- Take
categoryandtypeIdfrom the row the ordered pair's labels call returns, never assume a category: a custom object's unlabeled default (label: null) isUSER_DEFINED, a standard pair's isHUBSPOT_DEFINED.Measured - Association label rows carry
fromObjectTypeIdandtoObjectTypeIdasnull, so the object pair comes from the request path, never from the row.Measured - Up to 50 association labels can be defined per object pair, on Professional or higher.Source pending
GET /crm/associations/{v}/{from}/{to}/labelsreturns only that direction'stypeIds; the reverse order returns different ones, so read both orders of a pair.Measured- Association limits are written as
maxToObjectIdsper association type (Professional or higher) and read back asuserEnforcedMaxToObjectIds.Documented and measured
Spriggit uses these facts when it plans changes. See something out of date? Email [email protected]