---
title: "Update a WhatsApp template"
method: PUT
path: "/v1/design_studio/whatsapp/{id}"
tags: ["WhatsApp"]
---

# Update a WhatsApp template

`PUT /v1/design_studio/whatsapp/{id}`

## Request

- Base URL: `https://api.customer.io`
- URL: `https://api.customer.io/v1/design_studio/whatsapp/{id}`
- Auth: none declared

Update a WhatsApp template's name, folder, category, language, content, recipient, or sender. You only need to send the fields you want to change; Customer.io keeps the current value of any field you leave out.

Meta reviews a template's content, category, and language. After you submit the template to Meta, you can't change those three fields unless Meta rejects the template. To change an approved template, create a new template and submit that one instead. You can change the name, folder, recipient, and sender at any time.

Renaming a template only changes the name your team sees in Design Studio. It doesn't rename the template you submitted to Meta.

## Path parameters

- `id` string, uuid, required

## Request body

- object
  - `name` string: A new friendly name for the template.
  - `parent_folder_id` string, uuid, nullable: UUID of the folder you want to move the template into. Pass `null` to move the template to the root level.
  - `category` 'MARKETING' | 'UTILITY': The new Meta template category.
  - `language` string: The new Meta language code, like `en_US`.
  - `content` string: The new template, written as WhatsApp markup. See the `content` field on [Create a WhatsApp template](/integrations/api/design-studio/tag/whatsapp/createWhatsApp/) for the format.
  - `recipient` string: New liquid that resolves to the WhatsApp phone number of the person you're messaging, like `{{customer.phone}}`.
  - `sender_id` integer, nullable: The ID of the WhatsApp sender identity to send the template from. Pass `null` to clear the sender.

## Response `204`

WhatsApp template updated, no content returned

## Other responses

- `400`: The request is invalid due to malformed parameters, missing required fields, or constraint violations.
- `401`: Authentication failed due to a missing or invalid API key.
- `404`: The requested resource was not found.
- `409`: You tried to change the content, category, or language of a template you already submitted to Meta, and Meta hasn't rejected it. The error's `meta.status` holds the template's current Meta status.
- `422`: The liquid in `content` or `recipient` is invalid. Customer.io only checks the fields you send. Each error's `source.pointer` names the field that failed, as `/data/attributes/content` or `/data/attributes/recipient`.

## Changes

- **2026-10-28** `f33c07c62301`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference/changes/v1/design_studio/whatsapp/:id/put.md)

---

[API](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference.md) - [All operations](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference/llms.txt) - [OpenAPI document](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference/revisions/ac0b282053fe?raw)