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

# Send Workflow Email OTP

> Sends a one-time password via email to verify the user's email address as part of the workflow.
This is typically used during the EMAIL_CHECK verification process.

### Use Cases
- Email verification during user onboarding
- Confirming a user's email address before completing verification
- Adding an extra layer of authentication to the verification process

### Notes
- The OTP code is valid for 10 minutes
- Maximum 5 OTP requests per email address per hour
- Email templates can be customized in the Urtentic Dashboard




## OpenAPI

````yaml /api-reference/openapi.yml post /workflows/{workflowId}/email-otp
openapi: 3.0.0
info:
  title: Urtentic API
  version: '1.0'
  description: >
    # Introduction

    The Urtentic API provides comprehensive identity verification and workflow
    management capabilities. 

    It enables organizations to create customized verification workflows,
    perform identity checks, 

    and manage verification processes with features including liveness
    detection, 

    location intelligence, and document verification.


    ## Authentication

    All authenticated endpoints require two headers:

    - `Authorization: Bearer {API_KEY}` - Your API key

    - `X-CLIENT-ID: {CLIENT_ID}` - Your client ID


    API credentials can be generated from your Urtentic Dashboard under Settings
    > API Keys.


    ## Webhook Notifications

    Configure webhook URLs in your Urtentic Dashboard to receive real-time
    notifications

    about verification status changes. Webhooks include the verification ID and
    current status,

    allowing your system to react to verification completions or failures.


    ## Key Features

    - User and organization management

    - Customizable verification workflows

    - Multiple verification processes (Liveness, Location, Document, Watchlist
    Check, Email)

    - Analytics and reporting

    - Webhook notifications for verification results
  contact:
    name: Urtentic Support Team
    email: support@urtentic.com
    url: https://urtentic.com/support
  termsOfService: https://urtentic.com/terms
  license:
    name: Urtentic License
    url: https://urtentic.com/license
servers:
  - url: https://api.urtentic.com/api/v1
    description: Urtentic API
security: []
tags:
  - name: Identity
    description: >
      Management of verified identity data, including retrieval and validation
      of identity information.


      Endpoints in this category allow you to:

      - Retrieve verified identity details

      - Check identity verification status

      - Update identity information

      - Link identities across verification sessions
  - name: Processes
    description: >
      Configuration and management of individual verification process types that
      can be used in workflows.


      The Urtentic platform supports these verification processes:

      - **Document Verification**: OCR and authenticity checks for identity
      documents

      - **Liveness Detection**: Confirms a person is physically present and not
      using photos/videos

      - **Location Intelligence**: Verifies geographic location and environments

      - **Email Verification**: Validates email ownership through OTP

      - **Watchlist Check**: Screens identities against compliance databases
  - name: Verification
    description: >
      Core verification operations including starting verifications, submitting
      verification data, and retrieving results.


      Key operations include:

      - Starting new verification sessions

      - Submitting identity data for verification

      - Retrieving verification results

      - Validating inputs before submission

      - Tracking verification status
  - name: Webhook
    description: >
      Configuration and management of webhook endpoints for receiving real-time
      event notifications.


      The webhook system allows you to:

      - Receive real-time notifications about verification status changes

      - Configure multiple webhook endpoints for different environments

      - Specify which events trigger notifications

      - Verify webhook signature to ensure authenticity

      - Track webhook delivery and retry failed deliveries
  - name: Workflow
    description: >
      Creation and management of verification workflows, combining multiple
      verification processes into customized sequences.


      Workflows allow you to:

      - Define multi-step verification sequences

      - Configure country-specific document requirements

      - Set custom verification rules and thresholds

      - Create specialized flows for different use cases

      - Manage verification process order and dependencies
paths:
  /workflows/{workflowId}/email-otp:
    parameters:
      - schema:
          type: string
          format: uuid
        name: workflowId
        in: path
        required: true
        description: Unique identifier of the workflow
        example: 40f85c69-b27a-46e8-9115-691401acb5df
    post:
      tags:
        - Workflow
      summary: Send Workflow Email OTP
      description: >
        Sends a one-time password via email to verify the user's email address
        as part of the workflow.

        This is typically used during the EMAIL_CHECK verification process.


        ### Use Cases

        - Email verification during user onboarding

        - Confirming a user's email address before completing verification

        - Adding an extra layer of authentication to the verification process


        ### Notes

        - The OTP code is valid for 10 minutes

        - Maximum 5 OTP requests per email address per hour

        - Email templates can be customized in the Urtentic Dashboard
      operationId: post-workflows-workflowId-email-otp
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                key:
                  type: string
                  description: >
                    The email address or identifier to send the OTP to.

                    This should be the user's email address that will receive
                    the verification code.
                  example: user@example.com
              required:
                - key
            examples:
              request:
                value:
                  key: user@example.com
        description: |
          Request body containing the email address to send the OTP to.
      responses:
        '204':
          description: >
            OTP email sent successfully. No content is returned in the response
            body.
      security:
        - apiKeyAuth: []
components: {}

````