Skip to main content

Sole-trader party

The end-to-end journey for a SOLE_TRADER 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.

A sole trader is fully available (provision, get, update, delete, search). It is represented as a person with an ABN: the party carries entityType: SOLE_TRADER, and GET surfaces that type with the proprietor's identity plus abn.

End-to-end journey​

Provision drives the party PROSPECT → ACTIVE in a single call (see the party overview).

What differs for sole traders​

  • Represented as a person + ABN. GET returns entityType: SOLE_TRADER with the proprietor's identity (firstName, lastName, middleName, dateOfBirth) plus abn. Business-heavy fields (e.g. business description, commencement date) are not surfaced in this phase.
  • Update. PUT /v1/parties/{partyId} requires firstName, lastName, and dateOfBirth (400 GEN000000 otherwise) and carries entityDetails.abn.
  • No relationships. Relationship routes are company-only.