Proof requests

Proof templates are used to create proof requests. When a proof request is created, you will receive a URL which needs to be delivered to a holder's wallet application either as a link (in the "response_url" field) or displayed in a QR code for the wallet application to scan (conveniently pre-generated for you in the "qr" field). The holder's wallet will then generate a proof response and deliver it to the Truvera API which will check it for cryptographic correctness. Your integration paradigm will determine how you receive the verification response along with the verified attributes: either by polling or via a webhook.

To get a response by polling, check the proof-request details for when the "verified" attribute equals "true". At that point, the "presentation" field will contain the verified attributes as a JSON list.

When creating a proof request, you can optionally provide a verifier DID in order for the holder to know that your verifier is on their trust-list, such as in an ecosystem of trust.

Create proof request

This route uses a template ID and takes the PEX request you defined there.

Creates proof request

post
/proof-templates/{id}/request

Creates a proof request from this template

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
idstring · uuidRequired

Proof template UUID

Body
noncestringOptional

A unique nonce value used in the proof request.

Example: 123456
didstring · min: 32Optional

The DID that will be used as the verifier DID in the proof request

Example: did:cheqd:testnet:ac2b9027-ec1a-4ee2-aad1-1e316e7d6f59
Responses
200

Returns the information about the proof request

application/json
post
/proof-templates/{id}/request

Create proof request

This route lets you create a standalone proof request without storing a verification template first.

Create a new proof request

post
/proof-requests

Create a proof request

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Body

Represents a proof request payload in a verifiable credential system.

namestringRequired

Proof request name

Example: Proof request
cedarVerificationPolicystringOptional

Optional Cedar policy to run on verification

templatestring · uuidOptional

The unique identifier for the template.

Example: 37275574-7ea4-438d-b8ef-f8fc61dbf09e
noncestringOptional

Nonce or challenge for the presentation to match

Example: 1234567890
didstring · min: 32Optional

A DID

Example: did:cheqd:testnet:ac2b9027-ec1a-4ee2-aad1-1e316e7d6f59
Responses
200

Proof request created

application/json
post
/proof-requests

Get all proof requests

List all proof requests

get
/proof-requests
Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Query parameters
offsetinteger · int32Optional

How many items to offset by for pagination

Default: 0
limitinteger · int32 · min: 1 · max: 64Optional

How many items to return at one time (max 64)

Default: 64
Responses
200

A paged array of proof requests

application/json
get
/proof-requests

Get the details of an existing proof request

Get proof request

get
/proof-requests/{id}

Get the details of an existing proof request

Authorizations
Path parameters
idstring · uuidRequired

Proof request UUID

Responses
200

Returns the information about the proof request

application/json
get
/proof-requests/{id}

Delete the proof request

Delete proof request

delete
/proof-requests/{id}

Deletes the proof request and associated data

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
idstring · uuidRequired

Proof request UUID

Responses
200

Proof request will be deleted

No content

delete
/proof-requests/{id}

No content

Last updated

Was this helpful?