Skip to main content

Individual party

The end-to-end journey for an INDIVIDUAL party, from the caller's perspective. For the shared status machine and entity-type matrix see the party overview; for the call contract see endpoints → parties.

An individual is fully available: it can be provisioned, read, updated, deleted, and searched.

End-to-end journey​

Provision drives the party PROSPECT → ACTIVE in a single call (see the party overview); the response reports status: ACTIVE.

What differs for individuals​

  • Read shape. GET surfaces entityType: INDIVIDUAL with the person's identity (firstName, lastName, middleName, dateOfBirth) plus contact arrays. Phone countryCode is always +61 (Australian).
  • Provision fields. An individual is provisioned from person fields; an omitted name prefix defaults to Mx.
  • Relationships. An individual is never the owner of relationships — it can only be attached as a member of a COMPANY (see company).