Sign in

v8

latestOpenAPI 3.1.0raw.githubusercontent.com2026-07-05730512.7 KB
Trust Registry

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.

post/v1/relying-parties

Request body

namestring required

You set the relying party display name.

originstring uri required

You set the web origin for this relying party.

client_idstring

You optionally set the OpenID4VP (OpenID for Verifiable Presentations) client identifier.

trust_policystring

You optionally set the trust policy: tenant (default, inherit the tenant registry) or custom (per-relying-party trust rules).

Example request

{
  "name": "Campus Door",
  "origin": "https://door.acme.example",
  "client_id": "campus-door",
  "trust_policy": "tenant"
}

Response

The relying party was registered.

idstring uuid

You receive the UUID for this relying party registration.

namestring

You receive the relying party display name.

originstring uri

You receive the registered web origin for this relying party.

client_idstring

You receive the OpenID4VP (OpenID for Verifiable Presentations) client identifier. The captured value is an empty string when you do not set one.

statusstring

You receive the registration status for this relying party.

created_atstring date-time

You receive the timestamp when this relying party was registered.

trust_policystring

You receive the trust policy for this relying party: tenant (inherit the tenant trust registry) or custom (per-relying-party trust rules).

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"
}