Skip to content
Reselling Products

WhatsApp Template Error: “body: Parameter at index contains URL”

WhatsApp Template Error: "body: Parameter at index contains URL" Why this happens, and two ways to fix it. What This Means Your message template was…

1 min read245 words1 explained image
View as markdownOpen in ClaudeOpen in ChatGPT
Each image has a one line explanation. Switch to full detail for the step it belongs to, the fields and buttons involved, examples and the whole procedure.
On this page
  1. What This Means
  2. Why It Happens
  3. How to Fix It (Choose One)

WhatsApp Template Error: "body: Parameter at index contains URL"

Why this happens, and two ways to fix it.

What This Means

Your message template was approved without a URL inside the body's variable(s), but at send time you're putting a URL inside a body parameter (e.g., {{1}}). For anti-phishing and quality reasons, Meta does not allow full URLs inside body placeholders. Links must be part of the template itself or placed in buttons (with optional dynamic suffixes).

What This Means (image 1 of 1) What this shows WhatsApp Template Error: "body: Parameter at index contains URL" Why this happens, and two ways to fix it. What this shows Illustrates the "What This Means" section of "WhatsApp Template Error: “body: Parameter at index contains URL”". This screenshot appears in the "What This Means" section of "WhatsApp Template Error: “body: Parameter at index contains URL”". For context, this section explains: WhatsApp Template Error: "body: Parameter at index contains URL" Why this happens, and two ways to fix it. What This Means Your message template was approved without a URL inside the body's variable(s), but at send time you're putting a URL inside a body parameter (e.g., {{1}}). For anti-phishing…. This part of the guide covers 2 fields, listed below. Image 1 of 1
Fields in this part of the guide Button URL (base): https://example.com/order/Button text: "View Order"
Buttons and menus referenced withoutURL inside a body parameterbuttonsURL buttonfull URLCall-to-Action (CTA) Website button
All 4 steps in this procedure
  1. You're passing text like https://example.com/deal/123 into a variable {{1}}.
  2. The template's body was approved as plain text (variables expected to be names, codes, dates — not links).
  3. You used a URL shortener in a variable (many are blocked in parameters).
  4. You need a URL button instead of a body variable.

Why It Happens

  • You're passing text like https://example.com/deal/123 into a variable {{1}}.
  • The template's body was approved as plain text (variables expected to be names, codes, dates — not links).
  • You used a URL shortener in a variable (many are blocked in parameters).
  • You need a URL button instead of a body variable.

How to Fix It (Choose One)

Option A — Make the Link Static in the Body

Use a template where the full URL is written directly in the approved body (no variable).

Example body

"Hi {{1}}, please review your offer: https://example.com/offers"

When to use: The link is the same for everyone.

Option B — Use a CTA Website Button

Create/modify the template to include a Call-to-Action (CTA) Website button:

  • Button URL (base): https://example.com/order/
  • Button text: "View Order"

When to use: The URL needs a unique, per-recipient suffix (e.g., an order or contact ID) — the base URL is approved once, and only the dynamic suffix is filled in at send time.

Was this guide helpful?

Related guides