Skip to main content
Presentations

Send presentation

POST/v4/config/ows/holder/presentations/{presentationId}/response

Builds the Verifiable Presentation from the held credentials that the user chose and sends it to the verifier (the OpenID4VP Authorization Response). The record changes to presentation_acked, and the wallet sends the holder event ows.holder.presentation.sent. Each copy of a batch credential is presented only once.

  • Give credentials when the record has a dcqlQuery: one entry for each credential query to answer, with the id of the query and the chosen credentialId (or credentialIds for a query with multiple). For a query with claim_sets, also give claimIds: one option of claimSets of the chosen credential, from List matching credentials.

When the response mode asks for encryption, the wallet encrypts the response with encryptionAlgorithm. When the send fails, the wallet also sends an error response to the verifier, so that the verifier does not wait. After a good answer, send the user to responseRedirectUri when it is not empty, to finish the flow at the verifier.

With requiresTrustedRelyingParty on in the holder configuration, the wallet does not answer a request whose signer is not trusted, also for a record that it received before the setting was on.

Authorizations

  • Authorizationstringheaderrequired

    Your API key with the prefix ApiKey: ApiKey <your-api-key>. Get an API key.

    Scope:presentations:send

Path parameters

Body

application/json

The held credentials that the user chose, and the optional response encryption algorithm.

One of
  • bodyobject

    The choice for a DCQL query (the record has a dcqlQuery).

Response

application/json

The presentation record after the send.

  • presentationobject

    The presentation record, now presentation_acked, with the shared credentials in presentation and the redirect of the verifier in responseRedirectUri.