Skip to main content

Create Data Disclosure Agreement Template

POST 

/config/data-disclosure-agreement

Creates a Data Disclosure Agreement Template.

Request

Body

    dataDisclosureAgreementTemplate objectrequired

    Required fields to create a Data Disclosure Agreement Template

    language stringrequired

    ISO 639-1 language code (e.g. 'en' or 'sv')

    dataController objectrequired

    An organisation constituted as a legally defined entity in any jurisdiction

    publicKey string

    Data controller public key

    name stringrequired

    Possible values: <= 50 characters

    Data controller name

    legalId stringrequired

    Data controller legal identifier

    url urirequired

    Data controller URL

    industrySector stringrequired

    Possible values: <= 50 characters

    Data controller industry sector

    agreementPeriod integerrequired

    Possible values: >= 1

    Days for which the agreement is valid

    dataSharingRestrictions objectrequired

    Restrictions on how the data is shared. OBS! Object should be 'dataSharingRestrictions'

    policyUrl urirequired

    Where to find the policy

    jurisdiction stringrequired

    Jurisdiction where the data sharing restrictions apply

    dataRetentionPeriod integerrequired

    Possible values: >= 1

    How many days the data can be kept

    geographicRestriction stringrequired

    Where the data can be shared to

    storageLocation stringrequired

    Where the data is stored

    purpose string

    Possible values: <= 100 characters

    Required if active=true, unless present already from the draft version

    purposeDescription string

    Possible values: <= 500 characters

    Required if active=true, unless present already from the draft version

    lawfulBasis string

    Possible values: [contract]

    Required if active=true, unless present already from the draft version

    codeOfConduct urirequired

    URL to code of conduct

    dataAgreementId stringrequired

    ID of the connected Data Agreement

    dataAgreementRevisionId stringrequired

    ID of the connected Data Agreement Revision

    dataAgreementRevisionHash stringrequired

    Hash of the connected Data Agreement Revision

    presentationDefinitionId stringrequired

    ID of the connected Presentation Definition

    active booleanrequired

    Publish immediately if true

Responses

Data Disclosure Agreement Template created

Response Headers
  • Content-Type json

    Content-Type header

Schema
    dataDisclosureAgreementTemplate objectrequired

    A template outlines an agreement between a Data Source and Data Using Service that can be signed by both.

    context string[]required

    Array of URIs of JSON-LD contexts

    id stringrequired

    Unique Data Disclosure Agreement Template identifier

    type string[]required

    The Data Disclosure Agreement type from context

    language stringrequired

    ISO 639-1 language code (e.g. 'en' or 'sv')

    version stringrequired

    The version of this Data Disclosure Agreement Template

    templateId stringrequired

    Unique Data Disclosure Agreement Template identifier (derived from 'id')

    templateVersion stringrequired

    The version of this Data Disclosure Agreement Template (derived from 'version')

    dataController objectrequired

    An organisation constituted as a legally defined entity in any jurisdiction

    publicKey string

    Data controller public key

    name stringrequired

    Possible values: <= 50 characters

    Data controller name

    legalId stringrequired

    Data controller legal identifier

    url urirequired

    Data controller URL

    industrySector stringrequired

    Possible values: <= 50 characters

    Data controller industry sector

    agreementPeriod integerrequired

    Days for which agreement is valid

    dataSharingRestrictions objectrequired

    Restrictions on how the data is shared. OBS! Object should be 'dataSharingRestrictions'

    policyUrl urirequired

    Where to find the policy

    jurisdiction stringrequired

    Jurisdiction where the data sharing restrictions apply

    dataRetentionPeriod integerrequired

    Possible values: >= 1

    How many days the data can be kept

    geographicRestriction stringrequired

    Where the data can be shared to

    storageLocation stringrequired

    Where the data is stored

    purpose stringrequired

    Purpose of the Data Disclosure Agreement

    purposeDescription stringrequired

    Description of the Data Disclosure Agreement

    lawfulBasis stringrequired

    Possible values: [contract]

    Lawful basis for the Data Disclosure Agreement

    dataAttributes object[]required
  • Array [
  • id string

    Data attribute ID

    name stringrequired

    Name of the attribute, for instance "name" or "age"

    description stringrequired

    Description of the attribute

    sensitivity boolean

    Sensitivity of data attribute

    category string

    Category of data attribute

    scope string

    Scope required for data attribute

  • ]
  • codeOfConduct stringrequired

    URL to code of conduct

    dataAgreementId stringrequired

    ID of the connected Data Agreement

    dataAgreementRevisionId stringrequired

    ID of the connected Data Agreement Revision

    dataAgreementRevisionHash stringrequired

    Hash of the connected Data Agreement Revision

    active booleanrequired

    Whether the Data Disclosure Agreement is published or not

    presentationDefinitionId stringrequired

    ID of the connected Presentation Definition

    openApiSpecification object

    OpenAPI specification of the Data Agreement, defining available APIs for Data Using Services

    revision objectrequired

    A generic revision model captures the serialised contents of any schema's single row. This is then subject to 1) cryptographic signature and 2) auditing.

    Aside from the "successor" column, a revision should be considered locked.

    id stringrequired

    Revision ID

    schemaName stringrequired

    Possible values: [dataAgreement, policy, dataAgreementRecord]

    Previously "schema" but for technical reasons should be called "schemaName"

    objectId stringrequired

    The PK of the object that was serialised

    objectData stringrequired

    The object that is serialised

    signedWithoutObjectId boolean

    Indicates that objectId was left blank in serizalizedSnapshot when calculating serializedHash. objectId may subsequently be filled in.

    serizalizedSnapshot stringrequired

    Revisioned data (sed as JSON) as a dict. Apply JSON Canonicalization Scheme as per IETF RFC 8785. It contains all the fields of the schema except sucessorId, serializedHash, serializedSnapshot.

    serializedHash stringrequired

    Hash of serizalizedSnapshot (SHA-1)

    timestamp stringrequired

    Timestamp of when revisioning happened. It should be ISO 8601 UTC date time

    authorizedByIndividualId string

    Individual ID

    authorizedByOtherId string

    Reference to an admin user that has created this revision

    successorId string

    If this revision is no longer the latest revision, refer to its successor

    predecessorHash string

    Tamper-resistent artifact from previous record, copied from serializedHash

    predecessorSignature string

    Tamper-resistent artifact from previous record (we don't know if the previous record was signed or not)

Loading...