Skip to main content
GET
Download the signature evidence
Returns the evidence PDF of one signer, once they have signed. The path is in the signer’s signatures[].evidence_file, with signature_id already set.
Always pass signature_id. A Business Verification step can have several signers, and without it the route picks one of them.
The evidence PDF records the level and format, the signer and their verified identity session, the code confirmation, the IP address, each document with its original SHA-256, the adopted signature, every field’s value with its source and time, the final consent, the certificate, the timestamp and the SHA-256 of every signed file. See The evidence PDF. A signer who hasn’t signed returns 404 with signature_not_signed. After you delete the session, the route returns 404.

Authorizations

x-api-key
string
header
required

Your application's API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is missing, wrong, revoked or expired; 403 means the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key's workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys.

Path Parameters

sessionId
string<uuid>
required

The User Verification (KYC) or Business Verification (KYB) session.

Example:

"11111111-2222-3333-4444-555555555555"

nodeId
string
required

The Electronic Signature step: node_id of the item in signatures[].

Example:

"feature_signature"

Query Parameters

signature_id
string<uuid>

id of the signer's item in signatures[].

Response

The evidence PDF.

The response is of type file.