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

Order status update notification via WhatsApp API

The scenario sends the client a personalised WhatsApp template when the status of their order, application, or request changes.

Use case overview

The scenario sends the client a personalised WhatsApp template when the status of their order, application, or request changes. The message includes the client name, the process or entity being tracked, and the new status label. A static URL button opens the status page or customer portal.

Template example

Hello {{1}}, the status of your {{2}} has been updated to: {{3}}. You can view the full details on our website. Thank you for staying with us — we will notify you of any further changes.

View status
  • {{1}}
    customer name
  • {{2}}
    process or entity (e.g. order #12345, loan application, support ticket)
  • {{3}}
    new status label (e.g. Shipped, Under review, Approved)
  • “View status”
    button — fixed in the Meta template
WhatsApp Business API for status change notification

When to use it

Reach for this scenario when an order, application, or service request moves to a new stage and the client should learn about it before they call support or refresh a portal. It fits e-commerce and logistics teams tracking shipments, services and B2B businesses handling loan or visa reviews, and agencies connecting CRM, ERP, or custom portal status webhooks to WhatsApp outbound.

Fewer "where is my order?" calls
Three body variables carry the customer name, the process or entity being tracked, and the new status label, so the update lands in the client's WhatsApp chat instead of forcing a portal login or support call.
Updates without an open chat
The back office, CRM, or integration fires an approved template on the status change event, so the client hears about the new stage even when there is no active 24-hour WhatsApp session.
Full details one tap away
The static View status URL button is fixed in the Meta template and opens the status page or customer portal for anything the three body variables do not spell out.
Delivery logged for CRM follow-up
The system resolves the phone number from the status payload, sends the template, and logs the delivery result so back-office teams handle errors on the same record.

Workflow

  1. Status tracked

    The back office, CRM, or integration emits a status change event.

    status: "read"

  2. Resolves the recipient phone

    The system resolves the recipient phone number and status fields.

    status: "read"

  3. Build & send

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

    POST /sendTemplate

  4. Delivered

    The client receives the WhatsApp notification with the updated status.

    delivered

  5. Delivery result is logged

    Delivery result is logged; errors are handled according to platform rules.

    status: "read"

WhatsApp Business API for status change notification

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_PROCESS="___"         # {{2}} process name
TEST_STATUS="___"         # {{3}} status label

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_PROCESS=$TEST_PROCESS" \
            "TEST_STATUS=$TEST_STATUS"; 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}} process name → ${TEST_PROCESS}
# {{3}} status label → ${TEST_STATUS}
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_PROCESS}" },
        { "type": "text", "text": "${TEST_STATUS}" }
      ]
    }

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