Skip to main content
Data Agreement

Create data agreement

POST/v4/config/consent/data-agreement

Creates a data agreement: one purpose for which your organisation processes personal data, with its lawful basis, data policy and data attributes. Individuals give or refuse their consent to it through consent records.

With active: true the server publishes the data agreement: it saves the first revision with version 1.0.0, and individuals can consent to it. With active: false it saves a draft, without a revision; the answer then has a revision that the server made for the answer only (its id is empty).

The server sets the controller (your organisation), the IDs of the data attributes and the lifecycle. To link the data agreement to an OpenID4VC credential definition or presentation definition of your wallet, send dataExchange with the profile OID4VC.

Authorizations

  • Authorizationstringheaderrequired

    Your API key with the prefix ApiKey: ApiKey <your-api-key>. Get an API key.

    Scope:data-agreements:create

Body

application/json
  • dataAgreementobjectrequired

    The data agreement that you create or update. The server sets the ID, the version, the controller (your organisation) and the lifecycle. When active is true, purpose, purposeDescription, policy and dataAttributes are mandatory too.

Response

application/json

The data agreement and its revision.

  • dataAgreementobject

    A data agreement describes one purpose for which the organisation processes personal data (ISO/IEC TS 27560). Many individuals can consent to the same data agreement: each consent is a consent record.

  • revisionobject

    One saved version of a record (a data agreement, a policy, a consent record or a data disclosure agreement). Each change makes a new revision. The revision holds the record as JSON and a SHA-1 hash of the snapshot, and it links to the hash of the revision before it, so that you can detect a changed history. Only successorId changes after the server saves a revision.