Skip to main content
GET
Resolve DID

Headers

API-Version
string

Pin request, response, and webhook shapes to a specific dated API version (YYYY-MM-DD). Omit to use the version pinned to your API key (set when the key is created; new keys default to the latest version). New integrations should target the latest version.

Pattern: ^\d{4}-\d{2}-\d{2}$
Example:

"2026-07-06"

Path Parameters

did
string
required

The DID to resolve — a Humanos did:web identifier such as did:web:humanos.tech:org:<uuid> or did:web:humanos.tech:user:<uuid>. URL-encode the DID before placing it in the path (it contains : separators).

Example:

"did:web:humanos.tech:org:550e8400-e29b-41d4-a716-446655440000"

Response

The resolved W3C DID 1.1 Document for the requested DID.

@context
string[]
required

JSON-LD contexts. MUST include the DID core v1 context.

Example:
id
string
required

The DID this document describes

Example:

"did:web:humanos.tech:org:550e8400-e29b-41d4-a716-446655440000"

verificationMethod
object[]
required

Verification methods declared for this DID

authentication
string[]

Verification method IDs authorized for authentication

Example:
assertionMethod
string[]

Verification method IDs authorized for making assertions

Example:
keyAgreement
string[]

Verification method IDs authorized for key agreement

Example: