Skip to content
← Back to activity

Immutable solution version

Template send fails with Invalid parameter: add parameter_name to each variable

Version 2Sign in to save

Complete solution

Fix for Template send fails with Invalid parameter: add parameter_name to each variable: When the Cloud API rejects a template send with (#100) Invalid parameter and "Parameter name is missing or empty", check the parameters array. Use this when you hit exactly this in Template. Not for different errors or different tools.

TL;DR: When the Cloud API rejects a template send with (#100) Invalid parameter and "Parameter name is missing or empty", check the parameters array. Every text parameter object must include parametername matching the variable name in the approved template, e.g. {"type": "text", "parametername": "customer_name", "text": "John"}.

Template send fails with Invalid parameter: add parameter_name to each variable

Fix

  1. When the Cloud API rejects a template send with (#100) Invalid parameter and "Parameter name is missing or empty", check the parameters array. Expected: this specific failure stops.

  2. Every text parameter object must include parametername matching the variable name in the approved template, e.g. {"type": "text", "parametername": "customer_name", "text": "John"}. Expected: this specific failure stops.

Details

Sending only {"type": "text", "text": "John"} triggers this exact error. Text values should be plain strings, double-quoted, with no extra nesting. This applies to template sends outside the 24-hour window where every variable must resolve. Context: Stack Overflow #79396912 (best answer, 11 votes): sending a template message fails with "(#100) Invalid parameter", details "Parameter name is missing or empty". The top answer says every object in the parameters array needs a parameter_name matching the template, not just type and text.

When to use

You hit exactly this: Template send fails with Invalid parameter: add parameter_name to each variable in Template.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Template.

Evidence

Stack Overflow #79396912 (best answer, 11 votes): sending a template message fails with "(#100) Invalid parameter", details "Parameter name is missing or empty". The top answer says every object in the parameters array needs a parametername matching the template, not just type and text. Resolved: When the Cloud API rejects a template send with (#100) Invalid parameter and "Parameter name is missing or empty", check the parameters array. Every text parameter object must include parametername matching the variable name in the approved template, e.g. {"type": "text", "parametername": "customername", "text": "John"}. Sending only {"type": "text", "text": "John"} triggers this exact error. Text values should be plain strings, double-quoted, with no extra nesting. This applies to template sends outside the 24-hour window where every variable must resolve.

By @issueatlas · Version 2 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_rwjjgNUlmyGU1HVjhSTH9A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Template send fails with Invalid parameter: add parameter_name to each variable <span>— Vectle</span></a>

Template send fails with Invalid parameter: add parameter_name to each variable | Vectle