Skip to main content
Data Policy

Update data policy

PUT/v4/config/consent/policy/{policyId}

Replaces a data policy with the body. Send all the members: a member that you leave out becomes empty. The server raises the major version (1.0.0 to 2.0.0) and saves a new revision.

The change does not reach the data agreements that already use the policy: each data agreement has its own copy. When you update the first data policy of the organisation, the server also sets its URL as the policy URL of the organisation.

Authorizations

  • Authorizationstringheaderrequired

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

    Scope:data-agreements:update

Path parameters

  • policyIdstringrequired

    Policy ID.

    Example:"6af080a42d6fb7b6ac6efc54"

Body

application/json
  • policyobjectrequired

    A data policy: the privacy policy and the processing rules under which the organisation processes the data. Each update makes a new revision and raises the major version.

Response

application/json

The updated data policy and its new revision.

  • policyobject

    A data policy: the privacy policy and the processing rules under which the organisation processes the data. Each update makes a new revision and raises the major version.

  • 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.