💬 Shared WhatsApp Inbox on the new PlatformMore
1msg official logo

Company news broadcast via WhatsApp API template

The scenario sends a personalised WhatsApp template when the business publishes company or service news.

Use case overview

The scenario sends a personalised WhatsApp template when the business publishes company or service news. The message includes the contact's name, the news headline, and a short summary of what changed. A static URL button opens the full announcement page with details.

Template example

Hello, {{1}}! Company update: {{2}}. {{3}} Tap the button below to read the full announcement on our website.

Read announcement
  • {{1}}
    customer name
  • {{2}}
    company news headline or topic
  • {{3}}
    summary of what changed or the key detail
  • “Read announcement”
    button — fixed in the Meta template
WhatsApp Business API for company news broadcast

When to use it

Use this scenario when the business needs the full opted-in base to hear company or service news — a new branch, extended hours, a rebrand, a partnership, or a service update — and the copy is an announcement, not a discount pitch or a product going live. It fits retail networks sharing location news, SaaS platforms broadcasting policy or partnership updates, and agencies running company-news waves for client brands on WhatsApp.

Keep the base informed without an open chat
An approved MARKETING template reaches opted-in contacts outside the 24-hour window, so the news broadcast does not depend on an existing conversation.
Announcement copy, not a sales push
Three body variables carry the contact name, news headline, and change summary, so the message reads as company news rather than a promo line or product launch.
Distinct from per-account service notices
The broadcast targets the whole opted-in segment with company-level news, not a single customer's plan or account change like a utility service notification.
Less manual list work
CRM or automation loads the segment on publish day and the template goes out on that trigger, so operations does not retype the announcement for each contact.
Measurable announcement reach
Delivery results return to the sending system and button taps land on the announcement URL, so reach reports tie back to the same broadcast run.

Workflow

  1. Trigger

    Marketing or operations schedules a company news broadcast and defines the contact segment.

    event · triggered

  2. Capture event

    The system resolves each recipient phone and news personalisation fields.

    phone: "+…"

  3. Build & send

    A personalised news template is built with three body variables and a static URL button.

    POST /sendTemplate

  4. Delivered

    Each contact receives the WhatsApp company news message.

    delivered

  5. Status tracked

    Delivery and button taps are logged for announcement reach reporting.

    status: "read"

WhatsApp Business API for company news broadcast

Technical implementation

Prerequisites

  1. 1MSG API Key · How to get API Key
  2. WhatsApp Business account · How to Connect WABA
  3. WhatsApp Template · How to Approve WABA Template
  4. Customer opt-in · How to Manage Customers Consent

Code examples

#!/usr/bin/env bash
set -euo pipefail

# === Configuration (replace "___" placeholders) ===

API_BASE_URL="https://api.1msg.io"        # production 1MSG API base URL
CHANNEL_ID="___"                           # channel ID from 1MSG dashboard
API_TOKEN="___"                            # channel JWT token (Bearer)

TEMPLATE_NAME="___"                        # approved template name
TEMPLATE_NAMESPACE="___"                   # template namespace (required — send fails without it)
TEMPLATE_LANGUAGE="___"                    # template language code, e.g. "en"



# === Test data ===
TEST_PHONE="___"                 # client phone in international format
TEST_CUSTOMERNAME="___"         # {{1}} customer name
TEST_TOPIC="___"         # {{2}} topic or subject
TEST_DETAILS="___"         # {{3}} change details

PHONE_NORM="$(printf '%s' "$TEST_PHONE" | tr -cd '0-9')"

for pair in "CHANNEL_ID=$CHANNEL_ID" "API_TOKEN=$API_TOKEN" \
            "TEMPLATE_NAME=$TEMPLATE_NAME" "TEMPLATE_NAMESPACE=$TEMPLATE_NAMESPACE" \
            "TEMPLATE_LANGUAGE=$TEMPLATE_LANGUAGE" "TEST_PHONE=$TEST_PHONE" \
            "TEST_CUSTOMERNAME=$TEST_CUSTOMERNAME" \
            "TEST_TOPIC=$TEST_TOPIC" \
            "TEST_DETAILS=$TEST_DETAILS"; do
    val="${pair#*=}"
    if [ -z "$val" ] || [ "$val" = "___" ]; then
        echo "Missing configuration value: ${pair%%=*}" >&2
        exit 1
    fi
done

if [ -z "$PHONE_NORM" ]; then
    echo "Error: phone number has no digits after normalization" >&2
    exit 1
fi

URL="${API_BASE_URL%/}/${CHANNEL_ID}/sendTemplate"

# params carries body ONLY. Button text is fixed in the Meta template — no button param.

# {{1}} customer name → ${TEST_CUSTOMERNAME}
# {{2}} topic or subject → ${TEST_TOPIC}
# {{3}} change details → ${TEST_DETAILS}
read -r -d '' PAYLOAD <<JSON || true
{
  "phone": "${PHONE_NORM}",
  "template": "${TEMPLATE_NAME}",
  "namespace": "${TEMPLATE_NAMESPACE}",
  "language": { "policy": "deterministic", "code": "${TEMPLATE_LANGUAGE}" },
  "params": [
    {
      "type": "body",
      "parameters": [
        { "type": "text", "text": "${TEST_CUSTOMERNAME}" },
        { "type": "text", "text": "${TEST_TOPIC}" },
        { "type": "text", "text": "${TEST_DETAILS}" }
      ]
    }

  ]
}
JSON

RESPONSE="$(curl -s -w '\n%{http_code}' -X POST "$URL" \
    -H "Content-Type: application/json" \
    -H "Authorization: Bearer ${API_TOKEN}" \
    -d "$PAYLOAD")"

HTTP_CODE="$(printf '%s' "$RESPONSE" | tail -n1)"
BODY="$(printf '%s' "$RESPONSE" | sed '$d')"

case "$BODY" in
    *'"sent":true'*) ok=1 ;;
    *) ok=0 ;;
esac

if [ "$HTTP_CODE" -ge 200 ] && [ "$HTTP_CODE" -lt 300 ] && [ "$ok" -eq 1 ]; then
    echo "Message sent to client."
    echo "API response: $BODY"
else
    echo "Send failed. HTTP status: $HTTP_CODE" >&2
    echo "$BODY" >&2
    exit 1
fi

Response and delivery status

HTTP 2xx and JSON "sent": true mean 1MSG accepted the message for sending — not that it already reached the customer's phone. Save the id field (looks like wamid.…) to correlate delivery callbacks.

200 OKResponse
{
  "sent": true,
  "message": "Sent to [email protected]",
  "description": "Message has been sent to the provider",
  "id": "wamid.HBgLMzgwNjM5..."
}
  • sent

    Accepted for sending — not yet on the customer's phone

  • id

    Store it; delivery callbacks and hookInfo are keyed on this

Delivery statuses and webhooks →

Common errors

StatusAPI responseCauseFix
200Message was not sent: template is not definednamespace, template or language is missing from the request body.Send all three. Take namespace and the exact template name from GET /templates; language is an object: {"policy": "deterministic", "code": "en"}.
200template name (…) does not exist in <language>The template is approved in a different language than the one requested.Use the exact language code the template was approved in (for example es_MX is not the same as es). Check it in GET /templates.
200Message was not sent: provide chatId, phone, bsuid, or usernameNo recipient the channel could resolve.Pass exactly one recipient: phone (country code plus number, digits only), chatId (for example [email protected]) or bsuid.

All error codes →

Common questions

Related

Marketing Campaigns
Personal product picks via WhatsApp API template
The scenario sends a personalised WhatsApp marketing template when a recommendation engine or merchandiser prepares a curated selection of several items for a contact.
Marketing Campaigns
Offer deadline reminder via WhatsApp API
The scenario sends a personalised WhatsApp marketing template as the second touch of a promotion that is already running and about to close.
Marketing Campaigns
Segmented personal offers via WhatsApp API
The scenario sends a personalised WhatsApp marketing template when CRM splits an opted-in base into audience segments and assigns tailored offer terms to each.
Marketing Campaigns
Send content (guides, articles) via WhatsApp API
The scenario sends a personalised WhatsApp marketing template when the business publishes educational or entertaining content for opted-in contacts.
Marketing Campaigns
Post-purchase upsell message via WhatsApp API
The scenario sends a personalised WhatsApp marketing template shortly after a completed purchase when a follow-up offer is relevant — a refill, companion product, or the next service in the cycle.
Marketing Campaigns
Win-back message for inactive customers (API)
The scenario sends a personalised WhatsApp marketing template to an existing customer who bought or used the service before but has been inactive for months.
Marketing Campaigns
Seasonal sale broadcast via WhatsApp API
The scenario sends a personalised WhatsApp marketing template when a calendar-driven seasonal campaign goes live.
Marketing Campaigns
Event invitation via WhatsApp API template
The scenario sends a personalised WhatsApp marketing template to opted-in contacts when an upcoming public event is announced.

Build for WhatsApp in hours
without infrastructure hassle