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

# Send OTT message

> Send an OTT message via configured channel



## OpenAPI

````yaml POST /ott/messages
openapi: 3.0.3
info:
  title: NativeMessage API
  version: 1.0.0
  description: Complete API documentation for NativeMessage platform
  contact:
    name: NativeMessage Support
    email: support@nativemessage.com
servers:
  - url: https://api-message.nativehub.live/api/v1
    description: Production server
security:
  - BearerAuth: []
  - ApiKeyAuth: []
paths:
  /ott/messages:
    post:
      tags:
        - OTT Messages
      summary: Send OTT message
      description: Send an OTT message via configured channel
      operationId: sendOTTMessage
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - channel_id
                - to
              properties:
                channel_id:
                  type: string
                  format: uuid
                template_id:
                  type: string
                  format: uuid
                to:
                  type: string
                body:
                  type: string
                variables:
                  type: object
              example:
                channel_id: f8a9b0c1-d2e3-4567-fa89-012345678901
                template_id: a9b0c1d2-e3f4-5678-ab90-123456789012
                to: '+8801712345678'
                variables:
                  name: Alice
      responses:
        '201':
          description: OTT message sent successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OTTMessage'
        '400':
          description: Invalid request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    OTTMessage:
      type: object
      properties:
        id:
          type: string
          format: uuid
        tenant_id:
          type: string
          format: uuid
        channel_id:
          type: string
          format: uuid
        template_id:
          type: string
          format: uuid
        to:
          type: string
        body:
          type: string
        status:
          type: string
        provider_message_id:
          type: string
        error_message:
          type: string
        created_at:
          type: string
          format: date-time
      example:
        id: b0c1d2e3-f4a5-6789-bc01-234567890123
        tenant_id: c3d4e5f6-a7b8-9012-cdef-123456789012
        channel_id: f8a9b0c1-d2e3-4567-fa89-012345678901
        template_id: a9b0c1d2-e3f4-5678-ab90-123456789012
        to: '+8801712345678'
        body: Hello Alice, welcome to our service!
        status: delivered
        provider_message_id: wamid.abc123xyz
        created_at: '2026-02-14T11:00:00Z'
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
      example:
        error: Invalid request parameters
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key

````