Verify DID

This endpoint verifies whether a domain has a resolvable and self-consistent DID:web document at the standard location and returns the verification outcome in a machine-readable way.

This API is a domain-anchored identity preflight check that confirms whether a DID:web document is discoverable and consistent before higher-trust credential validation begins.

How to use in real verification workflows

  • Call POST /api/did/verify with issuer domain.
  • Require wellKnownFound === true.
  • Extract verification methods/keys from didDocument.
  • Verify VC/VP signatures against those keys.
  • Apply policy checks (issuer allowlist, expiration, revocation, credential schema, etc.).
Body Params

Verify DID request details

string
required

Domain or URL to verify (for example: blockpeer.net or https://blockpeer.net)

Headers
string

Unique key to ensure idempotency for API requests.

string

Unique external ID for tracking purposes, can be used for debugging and analytics.

Responses

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json