API reference
Subjects
/subjects
A subject is what events are about. Contacts are linked to subjects through /links. In the Standard lens a subject is, for example, “Subject 001” with reference SUB-2026-001.
GET/subjectsList · ?q ?external_refPOST/subjectsCreateshown →GET/subjects/{subject_id}ReadPATCH/subjects/{subject_id}Update · attributes replaced wholePOST/subjects/{subject_id}/deactivateDeactivate · no delete
POSTCreate a subject
Requires subjects:write. Unknown keys inside attributes are refused with 400: schemas are closed. There is no group field here; groups that follow an attribute are kept in step by Raven.
Body parameters
display_namestring · required · max 200
“Subject 001”.
external_refstring · optional · max 200
Your own identifier. “SUB-2026-001”. Trimmed as it is stored, and it is what ?external_ref= looks up exactly.
attributesobject · optionalVaries by pack
Checked against the instance's pack: its subject_schema. Choose a pack to see the keys. PATCH replaces the whole object; it does not merge.
The Standard lens has no pack behind it, so there are no keys to list.
Returns
201 with the subject. 400 for a bad or unknown attribute; the sentence names it. 409 if the reference is already on file — “That reference is already used by another record. Find it with ?external_ref= and update that record instead.”
Response body
One subject: the same fields in every pack. Press Response on the sample to see one whole.
FieldTypeDescription
iduuid
tenant_iduuidThe instance.
external_refstring | nullYour own id, as you sent it.
display_namestring
attributesobjectShaped by the instance's pack's subject_schema.Varies by pack
statusactive | inactive
created_atdatetime
updated_atdatetime
On failure the body is { error, code } instead.