Skip to main content
Documents for signing

Upload document for signing

POST/v4/config/ows/verifier/files

Uploads a PDF document that a holder signs with a qualified electronic signature from the EUDI Wallet, in a verification whose presentation definition has the transaction data type qes_data. Use the id or the fileExternalLink of the response in the transaction data of the verification request.

Send the file as multipart/form-data in the part file, with the part type application/pdf. The file must start with %PDF, its name must end with .pdf, and it can be at most 1 MB. An organisation can keep at most 10 documents: delete one before you upload the next.

These operations work without the Document Signing extension, and they share the documents with the document operations of the extension. Turning off the Document Signing extension deletes all the documents of the organisation.

Authorizations

  • Authorizationstringheaderrequired

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

    Scope:files:create

Body

multipart/form-data
  • filefilerequired

    The PDF document. Part type application/pdf, at most 1 MB.

Response

application/json

The document is stored.

  • idstring<uuid>

    The ID of the document.

    Example:"83cd38bc-3291-44a4-b40b-aa971275a4b5"

  • filenamestring

    The file name of the upload, without a path.

    Example:"docs-check-platform-contract.pdf"

  • fileExternalLinkstring<uri>

    The public link of the document at the wallet service, <service host>/organisation/<organisationId>/service/file/<id>. The EUDI Wallet downloads the document from it.

    Example:"https://demo-api.igrant.io/organisation/60905277-d953-4ef7-aa4c-cec413d00d93/service/file/83cd38bc-3291-44a4-b40b-aa971275a4b5"