client.* events
The lifecycle of a client: creation, edits, archiving, restoring and deletion.
The lifecycle of a client: creation, edits, archiving, restoring and deletion. A client is the organisation a project is done for, so a mirror of the registry subscribes to this family beside project.* to keep the two in step.
Every event in the family is scoped to the team and carries no project_id in the envelope: a client belongs to the team, not to one of its projects, so an endpoint confined to one project never receives these. The payloads are thin on purpose: the id, the name and what the transition itself carries, never a snapshot of the client. Read the clients endpoint for the record.
Background
Required ability
Tokens subscribing to client.* events need client:view at mint time.
Events
How is this guide?
Last updated on