Skip to main content

List all data agreements

GET 
/service/verification/data-agreements

This endpoint is used to list all data agreements available for an organisation defined in the consent building block. The results are paginated.

Request​

Query Parameters

    offset integerrequired

    Requested index for start of resources to be provided in response requested by client

    limit integerrequired

    Default value: 10

    Number of items returned per page. Requested number of resources to be provided in response requested by client

    revisionId stringrequired

    An object with id revisionId

Responses​

Response Headers
    Schema
      dataAgreements object[]
    • Array [
      • id string
      version string

      The version of this specification to which a receipt conforms

      controllerId string

      ID of the controller

      controllerUrl stringrequired

      URL of data controller (may be omitted if no data involved)

      controllerName stringrequired

      Name of data controller (may be omitted if no data involved)

      policy objectrequired

      Policy under which this DataAgreement shall be governed. When creating a data agreement, the latest policy can be used to fill the default value, and organisation admin can decide to change it in data agreement level

      id string
      name stringrequired

      Name of the policy

      version string

      Version of the policy. It can follow semver format.

      url stringrequired

      Permanent URL at which this very version of the Policy can be read, should not be allowed to change over time.

      jurisdiction string

      Jurisdiction

      industrySector string

      Industry sector

      dataRetentionPeriodDays integer

      Data retention period in days

      geographicRestriction string

      Geographic restriction

      storageLocation string

      Storage location

      thirdPartyDataSharing boolean

      Third party data sharing

      dataAttributes object[]

      "Data attribute contains specifications of exactly what is collected."

      purpose stringrequired

      Name of purpose

      purposeDescription stringrequired

      Description of purpose

      lawfulBasis stringrequired

      Possible values: [consent, legal_obligation, contract, vital_interest, public_task, legitimate_interest]

      Lawful basis of the agreement - consent / legal_obligation / contract / vital_interest / public_task / legitimate_interest

      methodOfUse stringrequired

      Possible values: [null, data_source, data_using_service]

      null/data_source/data_using_service

      dpiaDate string

      The date on which the DPIA report is generated after a DPIA

      dpiaSummaryUrl string

      The URl providing the DPIA result reports, summary etc that can be verified by any interested parties

      signature object

      Signature of authorizing party of DataAgreement. Note: Signatures may be chained in case of multiple signatures.

      id string

      Objects may be passed back by some API endpoints without an id (PK), denoting that they are a "draft", i.e. a Signature that is not yet stored in the database and only exist in transit.

      payload stringrequired

      The final payload that is signed, constructed as a JSON serialization of fields {verificationPayload: ..., verificationPayloadHash: ..., verificationMethod: ..., verificationArtifact: ..., verificationSignedBy: ..., verificationJwsHeader, timestamp: ..., signedWithoutObjectReference: ..., objectType: ..., objectReference: ...}. Serialized as a JSON dict. If the signature is generated before anything is stored in the database (and has a PK), then the objectReference should be omitted from the payload but filled in afterwards.

      signature stringrequired

      Signature of payload hash, the format of the signature should be specified by either verificationMethod or verificationJwsHeader

      verificationMethod stringrequired

      A well-known string denoting which method is used. Valid values: . We might expand this with a relation to which verification methods that are supported. There may be a minimal set of supported methods necessary.

      verificationPayload stringrequired

      Internally generated serialized version of the data referenced by objectType and objectReference - by extracting and serializing their data as JSON.

      verificationPayloadHash stringrequired

      Internally generated cryptographic hash of the value to be signed, i.e. the value of verificationPayload

      verificationArtifact string

      A verification artifact in the form of a scanned object, image, signature etc.

      verificationSignedBy stringrequired

      Because an identifier's information may change over time, there is a need to store that information at the time of signing. In case of a cryptographic signature, this field should contain some identifier for looking up or verifying the public key of the signing party. In case of a non-cryptographic signature, this field could contain a natural individual's names, personal number, email addresses - store a snapshot that binds to the signature at the time of signing. In case of a cryptographic signature, this may be the fingerprint of the individual's public key or in some cases, a token from the user's ID session.

      verificationSignedAs string

      DRAFT FIELD: Specifies the relationship between the authorizing signature and the invidual which the payload concerns. This is relevant for Consent Records. Possible values: "individual" / "delegate"

      verificationJwsHeader string

      Alternative to the verificationMethod, verificationHash and verificationSignature, give a JWS serialized object (RFC7515)

      timestamp stringrequired

      Timestamp of signature, currently this field isn't part of the payload so it's not tamper-proof.

      signedWithoutObjectReference boolean

      Indicates that objectReference was left blank in the serialized version that was signed.

      objectType string

      Possible values: [revision, signature]

      Name of the schema model that objectReference points to. Values: "signature" or "revision"

      objectReference string

      A symmetric relation / back reference to the objectType that was signed. We are currently just modelling signing another signature (a chain) or signing a Revision (which can be a revision of a consent record, an agreement, policy etc)

      active booleanrequired

      DataAgreement is active and new DataAgreementRecords can be created.

      forgettable booleanrequired

      DataAgreementRecord may be deleted when consent is withdrawn, as its existence is not necessary for auditability.

      compatibleWithVersionId string

      WIP: This field indicates that Data Agreement Records may be transferred from this compatible previous revision of the same DataAgreement.

      lifecycle stringrequired

      Possible values: [draft, complete]

      WIP: Current Lifecycle state of the DataAgreement. Lifecycle states are used to manage internal workflows and should not be assigned semantic meanings for active Data Agreement Records.

      dataUsingServices undefined[]
    • ]
      • pagination object
      currentPage integer

      Current page number

      totalItems integer

      Total number of items available

      totalPages integer

      Total number of pages based on limit

      limit integer

      Number of items per page

      hasPrevious boolean

      Indicates if there's a previous page

      hasNext boolean

      Indicates if there's a next page

    Loading...
    Last updated on by George J Padayatti