← ClaudeAtlas

kudosity-whatsapp-templateslisted

Use pre-approved WhatsApp templates correctly on the Kudosity platform — naming rules, positional parameters, locales, and the custom content type for media headers, buttons and anything the simple template shape can't express. Use when a template send fails validation, when a template needs an image or document, or when picking between template and custom content.
kudosity/skills · ★ 0 · Data & Documents · score 70
Install: claude install-skill kudosity/skills
# WhatsApp Templates Templates are how you start a WhatsApp conversation. Outside the 24-hour service window they are the *only* thing that delivers. This skill is about getting the template payload right. The payload goes to: - **Endpoint:** `POST https://api.transmitmessage.com/v2/whatsapp/messages` - **Header:** `x-api-key: {KUDOSITY_API_KEY}` — from the Kudosity dashboard under **Developers → API Settings** - **Body:** `sender` (optional), `recipient` (E.164), `content_type`, `content` — the last two are what this skill covers For the full send flow, the 24-hour window rule and SMS fallback, see `kudosity-whatsapp`. ## Templates are created outside this API There is no endpoint to create, submit or approve a template. Templates are registered in your WhatsApp Business account and **pre-approved by WhatsApp** before they can be sent. The API only *uses* them. So a template send failing is almost never a code problem. It's one of: 1. The template name doesn't exist or isn't approved yet 2. The parameter count doesn't match the template's placeholders 3. The locale doesn't match an approved language version 4. The template needs media or buttons, and you're using the simple `template` shape instead of `custom` ## Two ways to send a template | Shape | Use when | |---|---| | `content_type: "template"` | Text-only template with positional placeholders. Covers most sends. | | `content_type: "custom"` | Anything else — image or document header, buttons, carousels, expli