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

Catalog broadcast via WhatsApp marketing template

The scenario sends a personalised WhatsApp marketing template to opted-in contacts when the business publishes or refreshes its full catalog.

Use case overview

The scenario sends a personalised WhatsApp marketing template to opted-in contacts when the business publishes or refreshes its full catalog. The message includes the customer name, the company or brand name, and a short note about what the catalog covers. A static URL button opens the complete online catalog or price list in one tap.

Template example

Hello {{1}}! {{2}} has updated its catalog: {{3}}. Tap the button below to browse the full range of products and services in one place.

View catalog
  • {{1}}
    customer name
  • {{2}}
    company or brand name sharing the catalog
  • {{3}}
    catalog scope note (e.g. full assortment, updated price list)
  • “View catalog”
    button — fixed in the Meta template
WhatsApp Business API for product and service catalog broadcast

When to use it

Use this scenario when you already have an opt-in WhatsApp list and want contacts to see the complete catalog or price list — the whole assortment, not a discount promo and not a personalised product shortlist. It fits retail and wholesale sharing updated ranges with buyers, service businesses sending rate cards to clients, and agencies broadcasting client catalogs from CRM segments.

Full assortment in one tap outside the 24-hour window
An approved MARKETING template delivers the catalog link on WhatsApp even when no conversation is open, so contacts can browse the entire range without waiting for a session reply.
Catalog sends that name the customer and the brand
Three body variables carry the contact name, the company or brand, and what the catalog covers, so the message reads as a useful reference update rather than a generic blast.
One static link to the whole price list
A URL button fixed in the Meta template opens the online catalog or price list page, so the contact sees every category in one place instead of a back-and-forth product picker.
Less manual catalog distribution
CRM or marketing automation supplies the segment and personalisation fields, and the template goes out on that trigger — no rep rebuilds the list or retypes catalog notes for each contact.
Campaign delivery tracking
Delivery results are logged for campaign reach tracking, so marketing knows how many opted-in contacts received the catalog before measuring site visits or orders elsewhere.

Workflow

  1. Trigger

    Marketing or CRM selects an opted-in segment for the catalog broadcast.

    event · triggered

  2. Capture event

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

    phone: "+…"

  3. Build & send

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

    POST /sendTemplate

  4. Delivered

    Each opted-in contact receives the WhatsApp catalog message.

    delivered

  5. Status tracked

    Delivery results are logged for campaign reach tracking and follow-up.

    status: "read"

WhatsApp Business API for product and service catalog 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_COMPANYORSPECIALISTNAME="___"         # {{2}} company or specialist name
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_COMPANYORSPECIALISTNAME=$TEST_COMPANYORSPECIALISTNAME" \
            "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}} company or specialist name → ${TEST_COMPANYORSPECIALISTNAME}
# {{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_COMPANYORSPECIALISTNAME}" },
        { "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
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.
Marketing Campaigns
New arrivals broadcast via WhatsApp API
The scenario sends a personalised WhatsApp template when new items or a collection appear in the catalogue.
Marketing Campaigns
Promo campaign broadcast via WhatsApp API
The scenario sends a personalised WhatsApp template when marketing launches a visual campaign.
Marketing Campaigns
Send WhatsApp promotions via API (offer template)
The scenario sends a personalised WhatsApp marketing template to opted-in contacts when a promotional campaign starts.
Marketing Campaigns
Re-engage a cold lead via WhatsApp API template
The scenario sends a personalised WhatsApp template to a lead or customer who showed interest earlier but went inactive.

Build for WhatsApp in hours
without infrastructure hassle