# 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…

- Source: https://docs.ghlcustomercare.com/docs/reselling-products/whatsapp/whatsapp-template-error-body-parameter-at-index-contains-url
- Section: Reselling Products / WhatsApp
- Reading time: 1 min
- Images: 1, each explained below

---
# 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).

![URL in body parameter error](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155051772003/original/KEPgYVPEZhXjVxYEcMTTet1OnBTAXJDUHg.png)

**What This Means (image 1 of 1)**

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.
- Fields: Button URL (base): https://example.com/order/, Button text: "View Order"
- Controls: without, URL inside a body parameter, buttons, URL button, full URL, Call-to-Action (CTA) Website button

Full 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.

---

Documentation for GHL Customer Care. Support: support@ghlcustomercare.com