Party

PropertiesCopy Anchor Link

ObjectCopy Anchor Link

{
  "$id": "https://api.sb/quietcopy.com/parties/party_1",
  "$type": "Party",
  "name": "QuietCopy"
}

RelationshipsCopy Anchor Link

• A Party is bound by many Agreements: the Parties the Agreement holds to its terms, each from the moment it signs. boundBy, inverse binds.
• A Party issues many Mandates: the Party who grants a Mandate is its principal: the Agent acts for them, and each Action records them as for. issues, inverse issuedBy.
• A Party has many Referrals: the Party who sends a Referral earns its reward. referrals, inverse madeBy.
• A Party has many Screenings: a Party is screened before its first money move and again when its details change; every result stays. screenings, inverse screens.

VerbsCopy Anchor Link

1. createCreates a Party.
   POST /{namespace}/partiesdoParty.created
2. getReturns one Party by id.
   GET /{namespace}/parties/{id}readNo Event
3. listReturns Parties, newest first, one page at a time.
   GET /{namespace}/partiesreadNo Event
4. updateChanges the given properties of a Party.
   PATCH /{namespace}/parties/{id}doParty.updated
5. deleteDeletes a Party; its history is kept.
   DELETE /{namespace}/parties/{id}doParty.deleted
6. screenScreen checks a Party against official registers and restricted-party lists and keeps the result as a Screening.
   POST /{namespace}/parties/{party}/screendoParty.screened

PermissionsCopy Anchor Link

Which Access level may call each Verb. One-way Verbs wait their delay window.

Call itCopy Anchor Link

Screen the latest party.

ExampleCopy Anchor Link

A game studio orders a voice-over through a marketplace, so the studio is a Party to the Order. The producer who signs the usage Agreement is a Party to it.