---
updatedAt: 2026-10-30T08:58:01.000Z
agentTools:
  projectIndex: https://docs.wati.io/llms.txt
---

# Delete templates by name

Retained legacy exception: Delete a WhatsApp template by name, currently absent from V3.

Delete templates by name. DELETE /{tenantId}/api/v1/whatsApp/templates/{wabaId}/{name}.

### Permissions

For API access tokens and OIDC tokens, satisfy **at least one** of: `api`, `messagetemplate:write`. API access tokens may satisfy a listed scope through the configured scope hierarchy; OIDC tokens are checked against their scope claims. Legacy JWT authentication does not use this scope check. Authentication, role, tenant, and applicable feature or plan checks still apply. For HTTP 403, check the credential type, applicable scopes, roles, and workspace access; 403 does not always mean a missing scope. Authentication/authorization failures do not guarantee a JSON response body.

# OpenAPI definition

```json
{
  "openapi": "3.0.4",
  "info": {
    "title": "WATI API",
    "version": "2.6",
    "description": "Documentation contract version 2.6. Use V3 for supported business operations, adopting its request, response, defaults and pagination. Retain V1/V2 only for the business exceptions listed in Introduction. API route versions are independent of this artifact version.\n\nSend Authorization: Bearer <your-token> with the workspace credential and regional API host. API route version does not select the authentication mechanism. Endpoint scopes, roles, account availability and channel access still apply; consult Authentication and each operation.\n\nChannel support is operation-specific. GET /api/ext/v3/channels lists additional connected channels and may exclude the default WhatsApp number; do not infer full channel coverage or permission to send from discovery alone.\n\nInspect HTTP status and business result separately. Some operations report business failure or partial recipient failure in HTTP 200. Authorization errors may have no JSON body. A 429 can indicate a rate or usage limit. For unknown write outcomes, reconcile state before retrying; do not assume idempotency.\n\nCreate webhook subscriptions through the documented V2 exception or the dashboard, then manage them through V3. Use supported event types for the workspace and distinguish request acceptance from final message delivery.",
    "contact": {
      "name": "WATI Support",
      "url": "https://docs.wati.io"
    }
  },
  "servers": [
    {
      "url": "https://live-mt-server.wati.io",
      "description": "WATI API host. Legacy v1 and v2 endpoints require tenantId in the path; v3 endpoints do not."
    }
  ],
  "tags": [
    {
      "name": "Templates",
      "description": "Manage and send WhatsApp message templates."
    }
  ],
  "paths": {
    "/{tenantId}/api/v1/whatsApp/templates/{wabaId}/{name}": {
      "delete": {
        "tags": [
          "Templates"
        ],
        "summary": "Delete templates by name",
        "responses": {
          "200": {
            "description": "Delete template by name success",
            "content": {
              "application/json": {
                "schema": {
                  "type": "object",
                  "properties": {
                    "ok": {
                      "type": "boolean",
                      "description": "Indicates whether the delete operation was successful."
                    }
                  }
                },
                "example": {
                  "ok": true
                }
              }
            }
          },
          "400": {
            "description": "Delete template by name failed",
            "content": {
              "application/json": {
                "schema": {
                  "type": "object",
                  "properties": {
                    "ok": {
                      "type": "boolean",
                      "description": "Indicates the delete operation failed (always false in this response)."
                    },
                    "result": {
                      "type": "string",
                      "description": "Error message describing why the delete operation failed."
                    }
                  }
                },
                "example": {
                  "ok": false,
                  "result": "delete template failed..."
                }
              }
            }
          },
          "403": {
            "description": "Authorization failed. Check the Permissions section for the credential-specific scope rules, and check roles and workspace access. The response may have no body; do not require a JSON error envelope."
          }
        },
        "parameters": [
          {
            "in": "path",
            "name": "wabaId",
            "schema": {
              "type": "string"
            },
            "required": true,
            "description": "WhatsApp Business Account ID"
          },
          {
            "in": "path",
            "name": "name",
            "schema": {
              "type": "string"
            },
            "required": true,
            "description": "Template name"
          },
          {
            "name": "tenantId",
            "in": "path",
            "required": true,
            "description": "Your WATI workspace (tenant) ID. This required path segment identifies the WATI account for legacy v1 and v2 API requests.",
            "schema": {
              "type": "string"
            }
          }
        ],
        "operationId": "deleteWhatsAppTemplateByNameV1",
        "description": "Retained legacy exception: Delete a WhatsApp template by name, currently absent from V3.\n\nDelete templates by name. DELETE /{tenantId}/api/v1/whatsApp/templates/{wabaId}/{name}.\n\n### Permissions\n\nFor API access tokens and OIDC tokens, satisfy **at least one** of: `api`, `messagetemplate:write`. API access tokens may satisfy a listed scope through the configured scope hierarchy; OIDC tokens are checked against their scope claims. Legacy JWT authentication does not use this scope check. Authentication, role, tenant, and applicable feature or plan checks still apply. For HTTP 403, check the credential type, applicable scopes, roles, and workspace access; 403 does not always mean a missing scope. Authentication/authorization failures do not guarantee a JSON response body.",
        "x-wati-permissions": {
          "scopeRequirementGroups": [
            {
              "anyOf": [
                "api",
                "messagetemplate:write"
              ]
            }
          ],
          "groupOperator": "allOf",
          "appliesTo": [
            "ApiAccessToken",
            "OIDC"
          ],
          "legacyJwtScopeCheck": "skipped",
          "apiAccessTokenHierarchy": "configured-by-identity-provider",
          "oidcFallbackWhenNoEndpointScope": null,
          "sourceCommit": "03c6d4bc1590408c569e65602f969c6a596672e3"
        },
        "x-wati-documentation": {
          "discovery": "legacy-exception",
          "reason": "Delete a WhatsApp template by name, currently absent from V3."
        },
        "x-internal": false
      },
      "parameters": [
        {
          "name": "tenantId",
          "in": "path",
          "required": true,
          "description": "Your WATI workspace (tenant) ID. This required path segment identifies the WATI account for legacy v1 and v2 API requests.",
          "schema": {
            "type": "string"
          }
        }
      ]
    }
  },
  "components": {
    "securitySchemes": {
      "BearerAuth": {
        "type": "http",
        "scheme": "bearer",
        "description": "API token from your WATI Dashboard > API Settings. Pass as `Authorization: Bearer <token>`."
      }
    }
  },
  "security": [
    {
      "BearerAuth": []
    }
  ]
}
```