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

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.

Use case overview

The scenario sends a personalised WhatsApp marketing template when the business publishes educational or entertaining content for opted-in contacts. The message includes the customer name, the content topic or title, and a short teaser about the value inside. A static URL button opens the full guide, article, checklist, case study, or video in one tap.

Template example

Hello {{1}}! We picked something useful for you: {{2}}. {{3}} Tap the button below to read or watch the full piece.

Open content
  • {{1}}
    customer name
  • {{2}}
    content topic or title
  • {{3}}
    value teaser (what the reader will learn or gain)
  • “Open content”
    button — fixed in the Meta template
WhatsApp Business API for content engagement broadcast

When to use it

Use this scenario when you already have an opt-in WhatsApp list and want to share value-first content — a guide, article, checklist, case study, video, or tip — that keeps the audience warm without selling anything directly. It fits education brands sharing weekly tips, B2B teams sending how-to pieces between product cycles, and agencies running content engagement waves for client brands. It is not for company news about yourself, discount promos, or interactive nurture flows with quick replies.

Keep the channel warm without a sales pitch
An approved MARKETING template delivers educational or entertaining content outside the 24-hour window, so contacts hear from you with value instead of another discount line.
Content sends that name the reader and the topic
Three body variables carry the contact name, content title, and value teaser, so the message reads as a useful pick rather than a generic broadcast.
One static link to the full piece
A URL button fixed in the Meta template opens the guide, article, checklist, case study, or video page, so the contact consumes the content in one tap instead of a back-and-forth chat.
Less manual content distribution
CRM or content automation supplies the segment and personalisation fields, and the template goes out on that trigger — no rep rebuilds the list or retypes teasers for each contact.
Engagement tracking on content sends
Delivery results and link taps are logged for the broadcast run, so marketing knows how many opted-in contacts opened the piece before planning the next content wave.

Workflow

  1. Trigger

    Content or marketing selects an opted-in segment for the engagement broadcast.

    event · triggered

  2. Capture event

    The system resolves phone numbers and content personalisation fields for each contact.

    phone: "+…"

  3. Build & send

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

    POST /sendTemplate

  4. Delivered

    Each opted-in contact receives the WhatsApp content engagement message.

    delivered

  5. Status tracked

    Delivery and link taps are logged for engagement tracking and follow-up.

    status: "read"

WhatsApp Business API for content engagement 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_ADDITIONALINFO="___"         # {{3}} additional info

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_ADDITIONALINFO=$TEST_ADDITIONALINFO"; 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}} additional info → ${TEST_ADDITIONALINFO}
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_ADDITIONALINFO}" }
      ]
    }

  ]
}
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
Product launch announcement via WhatsApp API
The scenario sends a personalised WhatsApp marketing template when a single named product, service line, tariff, or feature goes live.
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
Company news broadcast via WhatsApp API template
The scenario sends a personalised WhatsApp template when the business publishes company or service news.
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.

Build for WhatsApp in hours
without infrastructure hassle