Unreleased documentation. These pages follow the main branch and can change before the next release. For supported guidance, use v0.46.0.
Receive the wallet's direct_post.jwt response
const url = 'https://example.com/v1/responses/example';const options = { method: 'POST', headers: {'Content-Type': 'application/x-www-form-urlencoded'}, body: new URLSearchParams({error: 'example', response: 'example', state: 'example'})};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/v1/responses/example \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data error=example \ --data response=example \ --data state=exampleAnonymous; the request identifier is a bearer capability. The form carries one encrypted response JWE, or a plain OAuth error. Answers use the OAuth error shape and never carry a description.
Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Request Bodyrequired
Section titled “Request Bodyrequired”object
Compact JWE (ECDH-ES; A128GCM or A256GCM).
Example generated
error=example&response=example&state=exampleResponses
Section titled “Responses”The response was accepted; an empty object
object
Example generated
{}Headers
Section titled “Headers”The W3C Trace Context version 0 field of the request, or a server-created one when the request carried none or an invalid or repeated one. tracestate is never answered.
The response was refused
object
Example
{ "error": "invalid_request"}Headers
Section titled “Headers”The W3C Trace Context version 0 field of the request, or a server-created one when the request carried none or an invalid or repeated one. tracestate is never answered.
The configured request deadline elapsed
object
Example generated
{ "detail": "example", "status": 1, "title": "example", "type": "https://example.com"}Headers
Section titled “Headers”The W3C Trace Context version 0 field of the request, or a server-created one when the request carried none or an invalid or repeated one. tracestate is never answered.
The body exceeds the response size limit
object
Example generated
{ "detail": "example", "status": 1, "title": "example", "type": "https://example.com"}Headers
Section titled “Headers”The W3C Trace Context version 0 field of the request, or a server-created one when the request carried none or an invalid or repeated one. tracestate is never answered.
Responses are arriving too quickly
object
Example
{ "error": "invalid_request"}Headers
Section titled “Headers”The W3C Trace Context version 0 field of the request, or a server-created one when the request carried none or an invalid or repeated one. tracestate is never answered.
The audit destination is stopped, the response is being recorded, or holding the presentation would pass the held-presentation byte budget
object
Example
{ "error": "invalid_request"}Headers
Section titled “Headers”The W3C Trace Context version 0 field of the request, or a server-created one when the request carried none or an invalid or repeated one. tracestate is never answered.
Cookies on Registry Stack
We use optional cookies to understand how you use the main Registry Stack website and this documentation. If you contact us, we may link this activity to your enquiry. You can change your choice at any time. Read the privacy policy.
Your browser asks sites not to track you, so optional tracking stays off.
We could not use or save that choice. Optional tracking remains off.