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

# Fire a proactive message on demand

> Send a proactive message into an existing conversation without waiting for a store/EMR event (e.g. a tracking update or a template from your own backend). Reuses the proactive pipeline, so the account's quiet hours and the proactive log apply. The event is recorded with source 'manual'. To message a contact with no conversation yet, create the conversation first.



## OpenAPI

````yaml /api-reference/voxys_proactive_swagger.json post /api/v1/accounts/{account_id}/proactive_messages
openapi: 3.1.0
info:
  title: Voxys Connect - Proactive Messaging APIs
  description: >-
    Proactive messages fired by connected commerce/EMR systems (COD prompts,
    shipment tracking, cart recovery, FHIR results, membership win-back) and an
    on-demand fire endpoint.
  version: 1.0.0
  contact:
    email: support@voxys.ai
  license:
    name: MIT License
    url: https://opensource.org/licenses/MIT
servers:
  - url: https://connect.voxys.ai
security:
  - userApiKey: []
tags:
  - name: Proactive Messaging
    description: Proactive message log, failure alerts, retry, and on-demand fire.
paths:
  /api/v1/accounts/{account_id}/proactive_messages:
    post:
      tags:
        - Proactive Messaging
      summary: Fire a proactive message on demand
      description: >-
        Send a proactive message into an existing conversation without waiting
        for a store/EMR event (e.g. a tracking update or a template from your
        own backend). Reuses the proactive pipeline, so the account's quiet
        hours and the proactive log apply. The event is recorded with source
        'manual'. To message a contact with no conversation yet, create the
        conversation first.
      operationId: fireProactiveMessage
      parameters:
        - $ref: '#/components/parameters/account_id'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - conversation_id
                - content
              properties:
                conversation_id:
                  type: integer
                  description: Target conversation id (caller must have access)
                content:
                  type: string
                  description: Message body (or template body)
                content_type:
                  type: string
                  description: text (default), input_select, template, etc.
                  default: text
                content_attributes:
                  type: object
                  description: >-
                    Template/interactive payload (template name, params,
                    buttons)
                event_type:
                  type: string
                  description: Log label (default 'manual', e.g. tracking, promo)
                  default: manual
      responses:
        '200':
          description: Message queued or sent
          content:
            application/json:
              schema:
                type: object
                properties:
                  id:
                    type: integer
                    description: Proactive event id
                  status:
                    type: string
                    description: sent or deferred (deferred = queued past quiet hours)
                  conversation_id:
                    type: integer
                    description: Target conversation id
        '401':
          $ref: '#/components/responses/unauthorized'
        '404':
          $ref: '#/components/responses/not_found'
        '422':
          $ref: '#/components/responses/unprocessable'
components:
  parameters:
    account_id:
      name: account_id
      in: path
      required: true
      schema:
        type: integer
      description: Numeric ID of the account
  responses:
    unauthorized:
      description: Authentication failed – invalid or missing api_access_token
    not_found:
      description: Resource not found
    unprocessable:
      description: Unprocessable entity – validation errors
      content:
        application/json:
          schema:
            type: object
            properties:
              error:
                type: string
  securitySchemes:
    userApiKey:
      type: apiKey
      in: header
      name: api_access_token
      description: >-
        All API requests must include the `api_access_token` header with a valid
        agent or administrator token.

````