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

# Create a message template

> Write a template and submit it to Meta for review. It starts `PENDING`; Meta approves or rejects it, usually within minutes, and the status updates by itself. Only an `APPROVED` template can be sent. Number the body’s values `{{1}}`, `{{2}}`, … and give one example value for each. Requires `whatsapp:write`.



## OpenAPI

````yaml /openapi.json post /v1/whatsapp/templates
openapi: 3.1.0
info:
  title: Wixzel Voice API
  version: '2026-09-01'
  description: >-
    APIs for agentic telephony. One API key, one balance, every voice engine.


    ## Authentication

    Send your key as `Authorization: Bearer wv_live_...`. Keys are scoped: grant
    only what an integration needs. There is no admin scope.


    ## Versioning

    The `/v1` prefix covers additive changes. Behavioural changes ship behind a
    dated `Wixzel-Version` header, and existing keys keep the behaviour they
    were created with.


    ## Money

    Amounts are integer **micro-USD** (1,000,000 = $1.00). Voice usage is billed
    per second, per token and per character, so a float dollar figure cannot
    represent it without disagreeing with the ledger.


    ## Errors

    Every error carries a stable `code` and a `request_id`. Match on `code`; the
    `message` is for humans and may change.
  contact:
    name: Wixzel Voice
    url: https://voice.wixzel.com
servers:
  - url: https://api.voice.wixzel.com
    description: Production
security: []
tags:
  - name: Calls
    description: Place calls and read what happened on them.
  - name: Realtime
    description: Talk to an agent from a browser or app, with no phone line.
  - name: Agents
    description: >-
      The prompt, voice and behaviour of a caller, and its mascot: the animated
      face people see on your share link, your website and in your apps.
  - name: Leads
    description: People to call, and data to merge into prompts.
  - name: Campaigns
    description: Call a list of leads with one agent.
  - name: Knowledge bases
    description: Facts an agent can draw on mid-call.
  - name: Phone numbers
    description: Numbers on your SIP trunks.
  - name: SIP trunks
    description: Your carrier connections.
  - name: Appointments
    description: Bookings, including ones agents make on calls.
  - name: Usage
    description: Itemised billing lines.
  - name: Billing
    description: Balance, ledger and top-ups.
  - name: API keys
    description: Create, scope and rotate keys.
  - name: Engines
    description: What the platform can serve, and what it costs.
  - name: Voices
    description: Cloned voices, made from your own recordings, for your agents to speak in.
  - name: Callers
    description: Who called your agents, where from and on what, and the blocklist.
  - name: Webhooks
    description: Where events are sent, and what happened when they got there.
  - name: MCP servers
    description: Other apps’ tools, for agents to use while they are on a call.
  - name: Tools
    description: >-
      Your own tools, for agents to use while they are on a call: a webhook to
      your server, or an action in the caller’s app.
  - name: WhatsApp
    description: >-
      WhatsApp business numbers, the agents that answer their chats, and
      messages agents send.
  - name: Meetings
    description: >-
      Agents in Zoom, Google Meet and Teams meetings, through your own Attendee
      account.
paths:
  /v1/whatsapp/templates:
    post:
      tags:
        - WhatsApp
      summary: Create a message template
      description: >-
        Write a template and submit it to Meta for review. It starts `PENDING`;
        Meta approves or rejects it, usually within minutes, and the status
        updates by itself. Only an `APPROVED` template can be sent. Number the
        body’s values `{{1}}`, `{{2}}`, … and give one example value for each.
        Requires `whatsapp:write`.
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateWhatsAppTemplate'
      responses:
        '201':
          description: The template, pending Meta’s review
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WhatsAppTemplate'
        '400':
          description: Invalid request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Missing or invalid API key
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: Key lacks the required scope
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: No such record
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '409':
          description: The number already has a template with this name and language
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '429':
          description: Rate limited. Retry after the interval in `Retry-After`.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - bearerAuth: []
components:
  schemas:
    CreateWhatsAppTemplate:
      type: object
      properties:
        account_id:
          type: string
          pattern: ^[0-9a-f]{24}$
          example: 6a96a3ead6e886d42462dd3e
        name:
          type: string
          pattern: ^[a-z0-9_]{1,512}$
          description: Lowercase letters, digits and underscores.
          example: visit_reminder
        language:
          type: string
          pattern: ^[a-z]{2,3}(_[A-Z]{2})?$
          default: en_US
          description: A WhatsApp language code, e.g. en_US, en, hi, ml.
          example: en_US
        category:
          type: string
          enum:
            - UTILITY
            - MARKETING
          description: >-
            UTILITY for confirmations, reminders and updates; MARKETING for
            offers. Meta may re-categorise it.
        header:
          type: string
          maxLength: 60
          description: An optional bold first line, plain text, no placeholders.
        body:
          type: string
          minLength: 1
          maxLength: 1024
          description: The message. Values go in as {{1}}, {{2}}, … in order.
          example: Hi {{1}}, a reminder of your visit on {{2}}.
        examples:
          type: array
          items:
            type: string
            minLength: 1
            maxLength: 200
          maxItems: 20
          default: []
          description: >-
            One sample value per placeholder, in order. Meta needs them to
            review the template.
          example:
            - Asha
            - Thursday at 4 pm
        footer:
          type: string
          maxLength: 60
          description: An optional small grey last line.
      required:
        - account_id
        - name
        - category
        - body
    WhatsAppTemplate:
      type: object
      properties:
        id:
          type: string
          pattern: ^[0-9a-f]{24}$
          example: 6a96a3ead6e886d42462dd3e
        object:
          type: string
          enum:
            - whatsapp_template
        account_id:
          type: string
          pattern: ^[0-9a-f]{24}$
          example: 6a96a3ead6e886d42462dd3e
        name:
          type: string
        language:
          type: string
          example: en_US
        category:
          type:
            - string
            - 'null'
          description: MARKETING, UTILITY or AUTHENTICATION.
          example: UTILITY
        status:
          type:
            - string
            - 'null'
          example: APPROVED
        body:
          type: string
          example: Hi {{1}}, your appointment is on {{2}} at {{3}}.
        parameter_count:
          type: integer
          description: How many values the body takes, in order.
        parameter_names:
          type: array
          items:
            type: string
          description: The names of the values, for templates with named parameters.
        header_format:
          type:
            - string
            - 'null'
        synced_at:
          type: string
          format: date-time
          description: ISO 8601, always UTC.
          example: '2026-09-01T12:00:00.000Z'
      required:
        - id
        - object
        - account_id
        - name
        - language
        - category
        - status
        - body
        - parameter_count
        - parameter_names
        - header_format
        - synced_at
    Error:
      type: object
      properties:
        error:
          type: object
          properties:
            type:
              type: string
              enum:
                - invalid_request_error
                - authentication_error
                - permission_error
                - rate_limit_error
                - insufficient_credits
                - not_found_error
                - conflict_error
                - api_error
            code:
              type: string
              description: Stable machine-readable code.
              example: agent_not_found
            message:
              type: string
              description: >-
                Human-readable explanation. Do not match on this — match on
                code.
            param:
              type: string
              description: Which field caused the failure, when applicable.
            doc_url:
              type: string
            request_id:
              type: string
              description: Quote this when asking for help.
              example: req_01HXYZ...
          required:
            - type
            - code
            - message
            - request_id
      required:
        - error
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Your Wixzel Voice API key: `Authorization: Bearer wv_live_...`. Keys are
        scoped; grant only what the integration needs.

````

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