Delete a registered verifier application instance
/v2/presentations/applications/{verifierApplicationId}/instances/{instanceId}Deletes a registered instance of a verifier application.
Deleted instances will no longer be able to interact with the platform or receive tokens, and any existing tokens will be revoked.
Application owners can use this endpoint to remove individual instances that are no longer needed or were registered by mistake, without affecting the entire verifier application or its other instances. This is useful for cleaning up test instances or managing specific devices, rather than deleting the whole application and all its associated instances.
Roles
Analytics Events
Authorization
bearerAuth In: header
Path Parameters
Unique identifier for the verifier application.
uuidUnique identifier for the registered verifier application instance.
uuidResponse Body
application/json
curl -X DELETE "https://example.com/v2/presentations/applications/281d20b3-42a3-40dd-b29a-115ff32b02b7/instances/1ef1f867-20b4-48ea-aec1-bea7aff4964c"How would you rate this page?
Retrieve a registered verifier application instance GET
Retrieves a registered instance of a verifier application.
Retrieve presentation session result GET
Retrieves the result of an online presentation session by providing the session's ID. When a holder responds to a verification request, the result indicates whether the presentation succeeded and whether the credentials were verified. The response can be a `PresentationSuccessResult` (holder completed the presentation workflow) or a `PresentationFailureResult` (holder was unable to complete the workflow). A successful presentation may include verified credentials, credential errors (requested credentials not provided), claim errors (specific claims that failed verification), or a combination of these outcomes. Your backend should validate that the returned `challenge` matches the challenge generated before starting the session to protect against session replay attacks. For OpenID4VP sessions, this endpoint returns a result only after the session's single-use response code has been exchanged. The Verifier Web SDK performs that exchange in the browser, in the cross-device modal and in `handleRedirectCallback()` on the same-device redirect, and it is otherwise a public request to `POST /v2/presentations/sessions/{sessionId}/result`. Calling this endpoint before the exchange returns `404`, even though the session completed and the result exists. Digital Credentials API sessions do not use a response code, and their results are retrievable as soon as the response has been processed. Results are short lived, currently five minutes from when the holder responds, after which this endpoint also returns `404`. Within that window the endpoint is repeatable, so retrieving a result does not consume it. Aborting an OpenID4VP session before its result is collected discards the result. For detailed information about result structures, error types, and complete examples, see the [handling verification results guide](https://learn.mattr.global/docs/verification/remote-web-verifiers/handling-verification-results).