Running Verifications
A verification session references a stored DCQL query by its id, so what production verifications request is governed by the stored, versioned query rather than by inline request bodies. Schemas are in the OID4VP Verifier API reference.
Run a verification session
The backend opens a session referencing the stored query and returns the authorization request URI a wallet opens (typically rendered as a QR code):
- Overview
- Request
- Response
01 Create verification request
Endpoint: POST /oid4vp/backend/auth/requests
Captured response: 201 Created
This captured endpoint is shown from the E2E run; it is not mapped to one of the generated EDK REST API reference pages.
The session is polled by correlation id. After the wallet presents, the status reaches authorization_response_verified and the response carries the disclosed claims:
- Overview
- Request
- Response
02 Poll verification status
Endpoint: GET /oid4vp/backend/auth/requests/OPAQUE-000042
Captured response: 200 OK
This captured endpoint is shown from the E2E run; it is not mapped to one of the generated EDK REST API reference pages.
- Overview
- Request
- Response
03 Cancel verification session
Endpoint: DELETE /oid4vp/backend/auth/requests/OPAQUE-000042
Captured response: 204 No Content
This captured endpoint is shown from the E2E run; it is not mapped to one of the generated EDK REST API reference pages.