# Request Phone Verification OTP

Requests an OTP to be sent via SMS to the phone number associated with the specified onboarding process (previously submitted via data-enrichment). Trigger this after the user confirms the enriched data presented by the Company.

Endpoint: POST /onboarding/{onboarding_process_ulid}/phone/send-otp
Version: 1.1.0
Security: user_bearer_auth

## Path parameters:

  - `onboarding_process_ulid` (string, required)
    The unique identifier (ULID) for the user's onboarding process.
    Example: "01ARZ3NDEKTSV4RRFFQ69G5FAV"

## Response 400 fields (application/json):

  - `code` (string, required)
    An application-specific error code string.
    Example: "INVALID_OTP"

  - `message` (string, required)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "The OTP provided is invalid or has expired."

## Response 401 fields (application/json):

  - `code` (string, required)
    An application-specific error code string.
    Example: "INVALID_OTP"

  - `message` (string, required)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "The OTP provided is invalid or has expired."

## Response 404 fields (application/json):

  - `code` (string, required)
    An application-specific error code string.
    Example: "INVALID_OTP"

  - `message` (string, required)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "The OTP provided is invalid or has expired."

## Response 500 fields (application/json):

  - `code` (string, required)
    An application-specific error code string.
    Example: "INVALID_OTP"

  - `message` (string, required)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "The OTP provided is invalid or has expired."


## Response 202 fields