Register a relationship type
Register a relationship type with explicit metadata (cardinality, description, bidirectional). Without this, types are auto-registered with empty metadata the first time a relationship of that shape is created. Set kind to person_to_co or co_to_co. Referenced custom object types must already exist — an unknown name returns 404 with fuzzy suggestions. Re-registering an existing type refines its metadata in place; omitted optional fields are preserved.
Authorizations
Organization API key, sent as Authorization: Bearer boom_org_....
Body
- Option 1
- Option 2
person_to_co Role label for the link (e.g. placed).
1 - 255An existing custom object type name.
1 - 255Multiplicity of the relationship type. For person→custom object, read it as person-to-object (e.g. ONE_TO_MANY = one person has many orders). For custom object→custom object, read it as parent-to-child.
ONE_TO_ONE, ONE_TO_MANY, MANY_TO_ONE, MANY_TO_MANY 1 - 1000Defaults to false.
Response
Relationship type registered (or refined if it already existed)
person_to_co, co_to_co Multiplicity of the relationship type. For person→custom object, read it as person-to-object (e.g. ONE_TO_MANY = one person has many orders). For custom object→custom object, read it as parent-to-child.
ONE_TO_ONE, ONE_TO_MANY, MANY_TO_ONE, MANY_TO_MANY true if the type was newly created, false if it already existed and was refined.
Present when kind is person_to_co.
Present when kind is co_to_co.
Present when kind is co_to_co.