> ## 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 Synthetic Signing Link and Issued OTP

> Test keys (or active sandbox keys) can retrieve an owned synthetic recipient link and its current issued code. Real recipients are excluded. Provide exactly one contact, id or internalId selector. Returns null code before issuance; completed, expired, revoked or exhausted flows are unavailable.



## OpenAPI

````yaml /versions/2026-11-02.yaml get /request/synthetic/{requestId}
openapi: 3.1.0
info:
  title: Humanos API
  description: Humanos API
  version: '1.0'
  contact: {}
servers:
  - url: https://api.humanos.tech
security: []
tags:
  - name: Agents
  - name: Requests
  - name: Credentials
  - name: Approval
  - name: User
  - name: Actions
  - name: Audit trail
  - name: DID
  - name: Call proof
  - name: Webhooks
paths:
  /request/synthetic/{requestId}:
    get:
      tags:
        - Requests
      summary: Get Synthetic Signing Link and Issued OTP
      description: >-
        Test keys (or active sandbox keys) can retrieve an owned synthetic
        recipient link and its current issued code. Real recipients are
        excluded. Provide exactly one contact, id or internalId selector.
        Returns null code before issuance; completed, expired, revoked or
        exhausted flows are unavailable.
      operationId: requests_getSyntheticRecipient
      parameters:
        - name: requestId
          required: true
          in: path
          description: Credential request identifier
          schema:
            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
        - name: contact
          required: false
          in: query
          description: >-
            Contact email or phone, including documented synthetic request
            aliases
          schema:
            type: string
        - $ref: '#/components/parameters/ApiVersion'
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SyntheticRecipientEntity'
        '403':
          description: Current key or synthetic recipient is unavailable
        '404':
          description: Synthetic recipient not found
components:
  parameters:
    ApiVersion:
      name: API-Version
      in: header
      required: false
      schema:
        type: string
        pattern: ^\d{4}-\d{2}-\d{2}$
        example: '2026-11-02'
      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:
    SyntheticRecipientEntity:
      type: object
      properties:
        subjectOtpId:
          type: string
          description: Exact synthetic recipient OTP identifier
        link:
          type: string
          description: Normal signing link for this synthetic recipient
        code:
          type:
            - string
            - 'null'
          description: Current issued OTP, or null before code delivery
      required:
        - subjectOtpId
        - link
        - code

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.