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

New arrivals broadcast via WhatsApp API

The scenario sends a personalised WhatsApp template when new items or a collection appear in the catalogue.

Use case overview

The scenario sends a personalised WhatsApp template when new items or a collection appear in the catalogue. The message includes the contact name, the arrivals topic or collection name, and a short highlight of what landed. A static URL button opens the new-items page.

Template example

Hello, {{1}}! Fresh arrivals are in: {{2}}. {{3}} Tap the button below to browse what just landed.

View new arrivals
  • {{1}}
    customer or contact name
  • {{2}}
    new arrivals topic or collection name
  • {{3}}
    short highlight of what landed or why to browse now
  • “View new arrivals”
    button — fixed in the Meta template
WhatsApp Business API for new arrivals broadcast

When to use it

Use this scenario when your catalogue gains new stock — a delivery that landed, a seasonal collection, or a refreshed menu — and you want opted-in contacts to hear about it before they discover it on their own. It fits fashion and retail drops, e-commerce restock announcements, and restaurants promoting new dishes to returning guests.

Traffic while new stock is fresh
When inventory or PIM flags new arrivals, the template reaches opted-in contacts on WhatsApp with the collection name and highlight in three body variables, so browse intent peaks while the drop is still news.
Announcements that name the drop
Three body variables carry the contact name, the arrivals topic, and what landed, so the message reads as a specific restock update rather than a generic catalogue blast.
One tap into the new-items page
A static URL button fixed in the Meta template opens the new-arrivals or collection page, so contacts can browse without waiting inside the 24-hour reply window.
No manual new-stock outreach
The catalogue-live event builds and sends the template automatically from PIM or inventory fields, so no one retypes collection names or remembers to notify each segment by hand.
Campaign delivery tracking
Delivery result is logged for marketing analytics or CRM follow-up, so the team knows whether the announcement landed before planning the next drop.

Workflow

  1. Trigger

    Inventory, PIM, or POS emits a new-arrivals or collection-live event for the segment.

    event · triggered

  2. Capture event

    The system resolves recipient phone numbers and personalisation fields from the campaign payload.

    phone: "+…"

  3. Build & send

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

    POST /sendTemplate

  4. Delivered

    Opted-in contacts receive the WhatsApp new-arrivals announcement.

    delivered

  5. Status tracked

    Delivery result is logged for marketing campaign analytics or CRM follow-up.

    status: "read"

WhatsApp Business API for new arrivals 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

Build for WhatsApp in hours
without infrastructure hassle