> ## 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.

# List localized contents

> Returns active content records (localization variants) for a broadcast message. Ordered with default content first, 
then localized content sorted by `locale` ascending and then `id` ascending.
There is one content record per locale as well as a default. The list response omits `content`. Use the dedicated endpoint to retrieve the contents.




## OpenAPI

````yaml /api-reference/campaigns-v2/campaigns-v2.yaml get /broadcasts/{broadcast_id}/messages/{message_id}/contents
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/{broadcast_id}/messages/{message_id}/contents:
    get:
      tags:
        - Broadcast Message Contents
      summary: List localized contents
      description: >
        Returns active content records (localization variants) for a broadcast
        message. Ordered with default content first, 

        then localized content sorted by `locale` ascending and then `id`
        ascending.

        There is one content record per locale as well as a default. The list
        response omits `content`. Use the dedicated endpoint to retrieve the
        contents.
      operationId: listBroadcastContent
      parameters:
        - name: broadcast_id
          in: path
          required: true
          description: Broadcast ID.
          schema:
            type: integer
        - name: message_id
          in: path
          required: true
          description: Message ID.
          schema:
            type: integer
        - 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'
      responses:
        '200':
          description: Broadcast message content returned.
          content:
            application/json:
              examples:
                default:
                  value:
                    - id: 200
                      message_id: 100
                      locale: null
                      is_default: true
                      name: Default
                      subject: Welcome to Acme
                      preheader_text: Glad you're here
                      created_at: '2026-03-01T10:00:00Z'
                      updated_at: '2026-03-01T10:00:00Z'
                    - id: 201
                      message_id: 100
                      locale: fr-FR
                      is_default: false
                      name: French
                      subject: Bienvenue chez Acme
                      preheader_text: Ravis de vous voir
                      created_at: '2026-03-01T10:00:00Z'
                      updated_at: '2026-03-01T10:00:00Z'
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/BroadcastContentListItem'
        '401':
          description: Missing or invalid API key.
        '403':
          description: The API key lacks permission to access this project.
        '404':
          description: Message belongs to a different broadcast.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NotFoundError'
      security:
        - ApiKeyAuth: []
components:
  schemas:
    BroadcastContentListItem:
      type: object
      description: |
        Content metadata for a broadcast message (one per locale / default). The
        list response omits `content`; fetch a single record for the body.
      required:
        - id
        - message_id
        - locale
        - is_default
        - name
        - created_at
        - updated_at
      properties:
        id:
          type: integer
        message_id:
          type: integer
        locale:
          type: string
          nullable: true
          description: BCP-47-style locale tag, or `null` for the default content variant.
        is_default:
          type: boolean
        name:
          type: string
          nullable: true
        subject:
          type: string
          nullable: true
        preheader_text:
          type: string
          nullable: true
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
    NotFoundError:
      type: object
      required:
        - error
      properties:
        error:
          type: string
          enum:
            - not_found
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: Accepts either a raw API key or `Bearer <key>`.

````