Marketing Messages

A specialised variant of Send Messages for MARKETING-category templates. Meta rejects marketing sends from the /messages endpoint when frequency caps would be hit; this endpoint accepts the same envelope plus the cap-aware flags.


POST /api/v25.0/{PHONE_NUMBER_ID}/marketing_messages
Authorization: Bearer pk_live_<your-key>
Content-Type: application/json

Request body

Same envelope as Send Messages for type: "template". The template’s category must be MARKETING.


{
  "messaging_product": "whatsapp",
  "to":                "+919999999999",
  "type":              "template",
  "template": {
    "name":     "diwali_promo",
    "language": { "code": "en_US" },
    "components": [
      {
        "type": "body",
        "parameters": [
          { "type": "text", "text": "Aditya" }
        ]
      }
    ]
  }
}

Response — 200

Identical to Send Messages.

Errors

In addition to the standard /messages errors, marketing sends can return:

Status	Example
`400`	`(#131056) Marketing message limit reached` — recipient has hit their per-day marketing cap

cURL


curl -X POST \
  "https://api.splashifypro.com/api/v25.0/$PHONE_NUMBER_ID/marketing_messages" \
  -H "Authorization: Bearer $SPLASHIFY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "messaging_product": "whatsapp",
    "to":                "+919999999999",
    "type":              "template",
    "template": {
      "name":     "diwali_promo",
      "language": { "code": "en_US" },
      "components": []
    }
  }'

Notes

Frequency caps are recipient-side. Meta limits how many marketing messages a recipient can receive across all businesses per day. Hitting the cap returns 400 — do not retry the same to until the cap resets.
Quality impact. Marketing sends count against the phone number’s quality rating. Low engagement (read-rate, block-rate) can flip it to YELLOW / RED and trigger Meta’s send throttles.