Register a relying party
Register a relying party verifier origin for wallet presentation requests. Didit ID uses the origin when a request flows through the W3C Digital Credentials API. The new registration starts as active.
Request body
Example request
{
"name": "Campus Door",
"origin": "https://door.acme.example",
"client_id": "campus-door",
"trust_policy": "tenant"
}Response
The relying party was registered.
Example response
{
"id": "66c7a3cd-de20-43ea-b06d-2f0e7a49fa5d",
"name": "Campus Door",
"origin": "https://door.acme.example",
"status": "active",
"created_at": "2026-07-02T23:33:35.172947+00:00",
"trust_policy": "tenant"
}Changes
Changed in 3 of the 8 revisions of this API.316
- ○
added the new optional request property
client_idnew-optional-request-property
- ○
added the new optional request property
trust_policynew-optional-request-property
- ○
added the optional property
trust_policyto the response with the201statusresponse-optional-property-added
- ○
- ▲
the
originrequest property type/format changed fromstring/tostring/urirequest-property-type-changed
- ▲
removed the success response with the status
200response-success-status-removed
- ●
removed the request property
client_idrequest-property-removed
- ○
removed the
activeenum value from thestatusresponse property for the response status201response-property-enum-value-removed
- ○
removed the
revokedenum value from thestatusresponse property for the response status201response-property-enum-value-removed
- ▲
- ▲
added required request body
request-body-added-required
- ○
added the success response with the status
201response-success-status-added
This revision also has 111 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲