Skip to main content
GET
Get User

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"

Query Parameters

contact
string

Verified contact value (email or phone)

Example:

"user@example.com"

id
string

User's VIA identifier

Example:

"did:web:humanos.tech:user:73ebefdd-a549-4873-aad9-def80c40c8c8"

internalId
string

Identifier to help you identify the user in your own system. We recommend using a unique value.

Example:

"internal-12345"

Response

The user's verified contacts (each with its DID), identity status, internal ID, organization-collected contacts, and registration date. Identity data itself is never returned by this endpoint.

contacts
SubjectIssuerEntity · object[]
required

List of verified contacts associated with the user

identityStatus
enum<string>
required

Identity status of the subject within the issuer

  • NONE: no identity verified
  • KYC: this user has an identity within your organization
  • HUMANOS: this user has a Humanos-verified identity
Available options:
NONE,
KYC,
HUMANOS
Example:

"HUMANOS"

organization
object
required

Contacts collected by your organization for this user. Identity data is never exposed through this API.

createdAt
string<date-time>
required

Date the subject was first registered

Example:

"2025-01-15T09:30:00.000Z"

internalId
string

Identifier to help you identify the user in your own system. We recommend using a unique value.

Example:

"internal-12345"