> ## Documentation Index
> Fetch the complete documentation index at: https://docs.humanos.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Get User

> Retrieves detailed information about a user. 
 Search by exactly one parameter: contact, id, or internalId. Only one must be provided.



## OpenAPI

````yaml /versions/2026-07-06.yaml get /user
openapi: 3.1.0
info:
  title: Humanos API
  description: Humanos API
  version: '1.0'
  contact: {}
servers: []
security: []
tags:
  - name: humanosApp
    description: ''
paths:
  /user:
    get:
      tags:
        - User
      summary: Get User
      description: |-
        Retrieves detailed information about a user. 
         Search by exactly one parameter: contact, id, or internalId. Only one must be provided.
      operationId: user_detail
      parameters:
        - name: contact
          required: false
          in: query
          description: Verified contact value (email or phone)
          schema:
            example: user@example.com
            type: string
        - name: id
          required: false
          in: query
          description: User's VIA identifier
          schema:
            example: did:web:humanos.tech:user:73ebefdd-a549-4873-aad9-def80c40c8c8
            type: string
        - name: internalId
          required: false
          in: query
          description: >-
            Identifier to help you identify the user in your own system. We
            recommend using a unique value.
          schema:
            example: internal-12345
            type: string
        - $ref: '#/components/parameters/ApiVersion'
      responses:
        '200':
          description: >-
            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.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SubjectIssuerEntity'
        '400':
          description: >-
            Invalid request parameters. Exactly one search parameter must be
            provided: contact, id, or internalId.
          content:
            application/json:
              schema:
                type: object
                properties:
                  statusCode:
                    type: number
                    example: 400
                  message:
                    type: string
                    example: >-
                      Exactly one search parameter must be provided: contact,
                      id, or internalId
                  error:
                    type: string
                    example: Bad Request
        '404':
          description: User not found
          content:
            application/json:
              schema:
                type: object
                properties:
                  statusCode:
                    type: number
                    example: 404
                  message:
                    type: string
                    example: User not found
                  error:
                    type: string
                    example: Not Found
components:
  parameters:
    ApiVersion:
      name: API-Version
      in: header
      required: false
      schema:
        type: string
        pattern: ^\d{4}-\d{2}-\d{2}$
        example: '2026-07-06'
      description: >-
        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.
  schemas:
    SubjectIssuerEntity:
      type: object
      properties:
        contacts:
          description: List of verified contacts associated with the user
          title: SubjectIssuerEntity
          type: array
          items:
            $ref: '#/components/schemas/ContactEntity'
        identityStatus:
          type: string
          description: |-
            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
          enum:
            - NONE
            - KYC
            - HUMANOS
          example: HUMANOS
        internalId:
          type: string
          description: >-
            Identifier to help you identify the user in your own system. We
            recommend using a unique value.
          example: internal-12345
        organization:
          description: >-
            Contacts collected by your organization for this user. Identity data
            is never exposed through this API.
          allOf:
            - $ref: '#/components/schemas/OrganizationDataEntity'
        createdAt:
          type: string
          description: Date the subject was first registered
          format: date-time
          example: '2025-01-15T09:30:00.000Z'
      required:
        - contacts
        - identityStatus
        - organization
        - createdAt
    ContactEntity:
      type: object
      properties:
        id:
          type: string
          description: Contact DID
          example: did:web:humanos.tech:user:73ebefdd-a549-4873-aad9-def80c40c8c8
        contact:
          type: string
          description: Verified contact value (email or phone)
          example: user@example.com
      required:
        - id
        - contact
    OrganizationDataEntity:
      type: object
      properties:
        contacts:
          description: Raw contact strings (email/phone) submitted by the organization
          example:
            - user@example.com
            - '+351912345678'
          type: array
          items:
            type: string
      required:
        - contacts

````