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

Seasonal sale broadcast via WhatsApp API

The scenario sends a personalised WhatsApp marketing template when a calendar-driven seasonal campaign goes live.

Use case overview

The scenario sends a personalised WhatsApp marketing template when a calendar-driven seasonal campaign goes live. The message includes the customer name, the season or occasion name, seasonal offer details, and the campaign end date. A static URL button opens the seasonal collection or sale landing page.

Template example

Hello {{1}}! Our {{2}} campaign is live: {{3}}. The seasonal sale runs until {{4}}. Tap the button below to explore the collection and shop now.

Shop seasonal sale
  • {{1}}
    customer name
  • {{2}}
    season or calendar occasion (Black Friday, New Year, back-to-school, summer sale)
  • {{3}}
    seasonal offer details (discount theme, featured categories, or gift focus)
  • {{4}}
    campaign valid until date
  • “Shop seasonal sale”
    button — fixed in the Meta template
WhatsApp Business API for seasonal campaign broadcast

When to use it

Use this scenario when a calendar season or holiday is the main reason to buy — Black Friday, New Year gift guides, back-to-school, or a summer clearance with a fixed campaign window — and you already have an opt-in WhatsApp list. It fits retail seasonal pushes, education enrollment waves, and agencies running named holiday campaigns for client brands from CRM segments. It is not for a generic discount without a season hook, a creative-only banner push, or a reminder that an unrelated offer is about to end.

Ride calendar buying moments on WhatsApp
An approved MARKETING template reaches opted-in contacts outside the 24-hour window, so the seasonal occasion itself can trigger the broadcast without waiting for an inbound message.
Campaigns that name the season and the window
Four body variables carry the contact name, occasion title, seasonal offer details, and campaign end date, so the message reads as a time-boxed seasonal event rather than a generic promotion.
One tap to the seasonal collection
A static URL button fixed in the Meta template opens the seasonal landing page, so contacts can shop the campaign assortment without relying on free-text replies.
Less manual seasonal list work
CRM or automation loads the opt-in segment when the campaign window opens and the template goes out on that trigger, so marketing does not retype occasion copy for each contact.
Measurable seasonal campaign delivery
Delivery results return to the sending system and are logged against the same broadcast run, so seasonal campaign reports tie back to the calendar window that started them.

Workflow

  1. Trigger

    Marketing schedules a seasonal campaign with a defined calendar window and contact segment.

    event · triggered

  2. Capture event

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

    phone: "+…"

  3. Build & send

    A personalised seasonal template is built with four body variables and a static URL button.

    POST /sendTemplate

  4. Delivered

    Each opted-in contact receives the WhatsApp seasonal campaign message.

    delivered

  5. Status tracked

    Delivery results are logged for seasonal campaign performance tracking.

    status: "read"

WhatsApp Business API for seasonal campaign 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
TEST_DATE="___"         # {{4}} date or time

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" \
            "TEST_DATE=$TEST_DATE"; 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}
# {{4}} date or time → ${TEST_DATE}
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}" },
        { "type": "text", "text": "${TEST_DATE}" }
      ]
    }

  ]
}
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
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
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
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
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.
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.

Build for WhatsApp in hours
without infrastructure hassle