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

# Create a broadcast

> Creates an unscheduled broadcast draft for your project, optionally seeding the default first message and default content from `message.content.body`. At this time `audience` and `schedule` fields are rejected with `422`.



## OpenAPI

````yaml /api-reference/campaigns-v2/campaigns-v2.yaml post /broadcasts
openapi: 3.0.3
info:
  title: Vero Open API v2
  version: 2.0.0
  description: >
    OpenAPI description for the API key-authenticated `api/v2` campaign and

    broadcast endpoints.


    Authentication uses the `Authorization` header. Both of these forms are
    accepted:


    - `Authorization: sk_valid_123`

    - `Authorization: Bearer sk_valid_123`

    - `revision: 2026-03-01`


    Campaign read endpoints require the `campaign:read` permission, and campaign

    write endpoints require the `campaign:write` permission.


    Broadcast read endpoints require the `broadcast:read` permission. A
    broadcast

    is a one-off or recurring message sent to an audience.
servers:
  - url: https://api.getvero.com/api/v2
security:
  - ApiKeyAuth: []
tags:
  - name: Broadcasts
  - name: Broadcast Messages
  - name: Broadcast Message Contents
  - name: Journeys
  - name: Journey Messages
  - name: Journey Message Contents
  - name: Campaigns
  - name: Campaign Messages
  - name: Campaign Message Contents
paths:
  /broadcasts:
    post:
      tags:
        - Broadcasts
      summary: Create a broadcast
      description: >-
        Creates an unscheduled broadcast draft for your project, optionally
        seeding the default first message and default content from
        `message.content.body`. At this time `audience` and `schedule` fields
        are rejected with `422`.
      operationId: createBroadcast
      parameters:
        - name: revision
          in: header
          required: false
          description: >-
            Optional dated API revision for the request. Must use `YYYY-MM-DD`
            format.
          schema:
            type: string
            pattern: ^\d{4}-\d{2}-\d{2}$
            example: '2026-03-01'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateBroadcastRequest'
            examples:
              minimal:
                summary: Minimal draft
                value:
                  name: Summer promo
              withContent:
                summary: Draft with initial content
                value:
                  name: Summer promo
                  channel: email
                  message:
                    from: hello@acme.com
                    content:
                      subject: 20% off this weekend
                      preheader_text: Sale ends Sunday
                      body:
                        html: <p>Hi {{ first_name }}</p>
        required: true
      responses:
        '201':
          description: Broadcast draft created.
          content:
            application/json:
              examples:
                default:
                  value:
                    id: 42
                    name: Summer promo
                    channel: email
                    schedule:
                      type: single
                      timezone_detection: false
                    status: draft
                    created_at: '2026-03-01T10:00:00Z'
                    updated_at: '2026-03-01T10:00:00Z'
              schema:
                $ref: '#/components/schemas/Broadcast'
        '422':
          description: Name is required and must be non-blank.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorList'
      security:
        - ApiKeyAuth: []
components:
  schemas:
    CreateBroadcastRequest:
      type: object
      description: >
        Create an unscheduled, unlaunched broadcast draft. Audience, segment,

        trigger, schedule, `send`, launch, and lifecycle fields are not
        supported

        and are rejected with `422 Validation error`.
      required:
        - name
      properties:
        name:
          type: string
          minLength: 1
          maxLength: 255
          description: Broadcast name. Trimmed before validation; must be non-blank.
        channel:
          type: string
          enum:
            - email
            - sms
            - push
          default: email
          description: |
            Messaging channel. Defaults to `email` when omitted. Supply the
            matching channel when the initial content is for `sms` or `push`.
        message:
          type: object
          nullable: true
          description: |
            Optional initial message. When present it initialises the
            server-provisioned default first message and default content.
          properties:
            from:
              type: string
              nullable: true
              description: |
                Sender email address (email channel). Must match an existing
                verified sender for the project, otherwise `422`.
            reply_to:
              type: string
              nullable: true
            content:
              type: object
              properties:
                subject:
                  type: string
                  nullable: true
                preheader_text:
                  type: string
                  nullable: true
                name:
                  type: string
                  nullable: true
                body:
                  $ref: '#/components/schemas/BroadcastContentBody'
                  description: |
                    Initial content body. Exactly one key valid for the channel
                    (`mjml`/`html`/`text` for email, `text` for sms, `payload`
                    for push); a mismatch returns `422`.
              additionalProperties: false
          additionalProperties: false
      additionalProperties: false
    Broadcast:
      type: object
      description: 'A broadcast: a one-off or recurring message sent to an audience.'
      required:
        - id
        - name
        - channel
        - schedule
        - status
        - created_at
        - updated_at
      properties:
        id:
          type: integer
        name:
          type: string
          description: Broadcast name.
        channel:
          type: string
          enum:
            - email
            - sms
            - push
          description: Delivery channel.
        schedule:
          type: object
          description: >
            Scheduling details for the broadcast. `type` indicates whether the

            broadcast is sent once or on a recurring schedule. Additional

            scheduling fields (such as `scheduled_at`, `cron`,

            `next_scheduled_at`, `batches`, and `timezone_detection`) may also
            be

            present.
          required:
            - type
          properties:
            type:
              type: string
              enum:
                - single
                - recurring
              description: >-
                `single` for a one-off broadcast, `recurring` for a broadcast
                sent on a repeating schedule.
          additionalProperties: true
        status:
          type: string
          enum:
            - draft
            - scheduled
            - sending
            - sent
            - cancelled
            - active
            - paused
            - archived
          description: >-
            Broadcast status. `archived` is returned for archived broadcasts on
            the detail endpoint.
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
    ErrorList:
      type: object
      required:
        - errors
      properties:
        errors:
          type: array
          items:
            type: object
            required:
              - message
            properties:
              message:
                type: string
    BroadcastContentBody:
      type: object
      description: >
        The deliverable body for a content record. Exactly one of `mjml`,
        `html`,

        `text`, or `payload` is present, depending on the message channel: email

        uses `mjml`/`html`/`text`, SMS uses `text`, push uses `payload`.
      properties:
        mjml:
          type: string
          nullable: true
        html:
          type: string
          nullable: true
        text:
          type: string
          nullable: true
        payload:
          type: object
          nullable: true
          additionalProperties: true
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: Accepts either a raw API key or `Bearer <key>`.

````