Skip to main content
PATCH
Approve or reject a presentation.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string
required

Body

application/json
status
enum<string>
required

approved shares the credentials in the holder's current selection with the verifier; rejected declines without sharing anything. Both are final and only valid while the presentation is pending (409 otherwise). To change which credentials get shared, PATCH .../picker first.

Available options:
approved,
rejected
Example:

"approved"

Response

200 - application/json

Updated presentation.

data
object
required

The lean presentation resource: lifecycle state and verifier identity. Everything about choosing credentials — what the verifier asks for, what the wallet can offer, what the holder picked — lives on the picker subresource (GET /presentations/{id}/picker).

meta
object
errors
object[]