Consent

PropertiesCopy Anchor Link

ObjectCopy Anchor Link

{
  "$id": "https://api.sb/petpantry.shop/consents/consent_1",
  "$type": "Consent",
  "basis": "Example basis",
  "region": "Example region",
  "withdrawnAt": "2026-10-22T12:00:00Z"
}

RelationshipsCopy Anchor Link

• A Consent covers one Purpose: the Purpose the Consent permits processing for, and nothing beyond it. covers, inverse consents.
• A Consent is given by one Contact: a Contact grants Consents, each for one Purpose, with its basis and expiry. givenBy, inverse gives.

VerbsCopy Anchor Link

1. createCreates a Consent.
   POST /{namespace}/consentsdoConsent.created
2. getReturns one Consent by id.
   GET /{namespace}/consents/{id}readNo Event
3. listReturns Consents, newest first, one page at a time.
   GET /{namespace}/consentsreadNo Event
4. updateChanges the given properties of a Consent.
   PATCH /{namespace}/consents/{id}doConsent.updated
5. withdrawWithdraw ends a Consent at once: processing for its Purpose stops, and the record is kept.
   POST /{namespace}/consents/{consent}/withdrawdoConsent.withdrawn

PermissionsCopy Anchor Link

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

Call itCopy Anchor Link

Withdraw the latest consent.

ExampleCopy Anchor Link

A visitor ticks a box for product updates on a pricing Page. The Consent records the marketing Purpose, the notice shown, the time, and a two-year expiry.