List presentation definition
GET/v2/config/digital-wallet/openid/sdjwt/presentation-definitions
Lists the presentation definitions of the organisation. The server sorts them by updatedAt and uses sortOrder for the direction.
Each item holds the presentation definition and the verification counters for that presentation definition. In this list the id of each item equals its presentationDefinitionId.
The response also holds verificationHistoryStats. These counters cover every verification exchange record of the organisation, not only the current page.
Set skipCounts to true to skip the per item counters. The server then returns zero for every counter of every item, and the answer is faster.
search finds a presentation definition by its label or by its presentationDefinitionId. The search is not case-sensitive.
Request
Query Parameters
Default value: 0
Number of records to skip for pagination. A negative or unreadable value falls back to 0.
Default value: 10
Maximum number of records to return per page.
Search term to filter results by
Possible values: [desc, asc]
Default value: desc
Sort order for the returned records (ascending or descending).
Possible values: [payment_data, payment, login_risk_transaction, login_risk_transaction_non_ts12, account_access, emandate, data_agreement_record, data_disclosure_agreement_record, qes_data]
Filter by the transaction data type of the presentation definition. The server compares this value with transactionDataDefinitionType.
Default value: false
Set to true to skip the per item verification counters. Every counter of every item is then zero. Use this option for a faster answer.
Header Parameters
Optional. Unique identifier of the sandbox organisation to use for this request. When you send this header, the service runs the operation in the context of the named sandbox organisation, that is, against the wallet of that sandbox organisation and not against the main wallet of the organisation. Leave the header out to use the main wallet.
The service reads this header only when you authenticate with a bearer access token. When you authenticate with an API key, the service takes the sandbox organisation from the API key and ignores this header. To run an API-key call in a sandbox organisation, bind the key to the sandbox organisation with PUT /v2/config/admin/apikey/{apiKeyId}/sandbox-org instead.
X-SubwalletId is the deprecated name of this header. The service continues to accept it, but X-SandboxOrgId wins if you send both headers.
The sandbox organisation must exist, must belong to your organisation and must be deployed. An unknown identifier, an identifier of a sandbox organisation that is not deployed, and an identifier that belongs to a different organisation all make the call fail with HTTP 400.
Responses
- 200
- 400
- 401
- 500
The server listed the presentation definitions.
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
Presentation definitions for the current page. The array is empty when the organisation has no presentation definition.
pagination objectrequired
Current page number
Total number of items available
Total number of pages based on limit
Number of items per page
Indicates if there's a previous page
Indicates if there's a next page
verificationHistoryStats objectrequired
Counters for every verification exchange record of the organisation. The filters and the pagination do not change these values. A record can be in more than one counter, so the counters do not add up to total.
Number of verification exchange records.
Number of records with status presentation_acked.
Number of records with status request_sent or request_received.
Number of records with status presentation_acked and verified equal to false.
Number of records whose Authorization Request expired.
{
"presentationDefinition": [
{
"id": "string",
"openIdOrganisationId": "string",
"presentationDefinitionId": "string",
"label": "string",
"dcqlQuery": {},
"transactionDataDefinitionType": "",
"createdAt": 0,
"updatedAt": 0,
"version": "version_01",
"kid": "string",
"trustAnchor": "did:key",
"scope": "string",
"responseType": "vp_token",
"clientIdScheme": "redirect_uri",
"directPostRedirectUri": "string",
"responseMode": "direct_post",
"dcApiRequestType": "signed",
"expectedOrigins": [
"string"
],
"encryptedResponseEncValuesSupported": [
"A128CBC-HS256"
],
"systemManaged": true,
"extentionEnabled": true,
"presentationDefinition": {},
"totalCountOfVerificationHistory": 42,
"verificationBreakdown": {
"total": 42,
"presentationReceived": 30,
"requestPending": 9,
"verificationFailed": 3,
"expired": 2
}
}
],
"pagination": {
"currentPage": 1,
"totalItems": 25,
"totalPages": 3,
"limit": 10,
"hasPrevious": false,
"hasNext": true
},
"verificationHistoryStats": {
"total": 128,
"presentationReceived": 96,
"requestPending": 24,
"verificationFailed": 5,
"expired": 8
}
}
The organisation is unknown, or the digital wallet deployment is not resolved.
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"errorCode": 400,
"errorDescription": "Bad input parameter"
}
Unauthorized
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"errorCode": 400,
"errorDescription": "Bad input parameter"
}
The server could not read the page of presentation definitions.
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"errorCode": 400,
"errorDescription": "Bad input parameter"
}