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

# Send template messages(CSV)

Compatibility reference for existing integrations. Parse CSV client-side into V3 recipients batches; CSV transport is not a separate messaging capability. Recommended V3 route: `/api/ext/v3/messageTemplates/send`.

Send template messages(CSV). POST /{tenantId}/api/v1/sendTemplateMessageCSV.

### 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": "Messages (v1)",
      "description": "Send and retrieve WhatsApp messages via the v1 API."
    }
  ],
  "paths": {
    "/{tenantId}/api/v1/sendTemplateMessageCSV": {
      "post": {
        "tags": [
          "Messages (v1)"
        ],
        "summary": "Send template messages(CSV)",
        "operationId": "SendTemplateMessageCsv",
        "parameters": [
          {
            "name": "template_name",
            "in": "query",
            "description": "Defined in the Template Message under Broadcast",
            "required": true,
            "schema": {
              "type": "string"
            }
          },
          {
            "name": "broadcast_name",
            "in": "query",
            "description": "Broadcast Name",
            "required": true,
            "schema": {
              "type": "string"
            }
          },
          {
            "name": "channelNumber",
            "in": "query",
            "description": "Channel phone number to select the channel context (optional)",
            "schema": {
              "type": "string"
            }
          },
          {
            "name": "tenantId",
            "in": "path",
            "required": true,
            "schema": {
              "type": "string"
            },
            "description": "Your WATI workspace (tenant) ID. This required path segment identifies the WATI account for legacy v1 and v2 API requests."
          }
        ],
        "requestBody": {
          "content": {
            "multipart/form-data": {
              "schema": {
                "required": [
                  "whatsapp_numbers_csv"
                ],
                "type": "object",
                "properties": {
                  "whatsapp_numbers_csv": {
                    "type": "string",
                    "description": "Whatsapp Numbers CSV",
                    "format": "binary"
                  }
                }
              },
              "encoding": {
                "whatsapp_numbers_csv": {
                  "style": "form"
                }
              }
            }
          }
        },
        "responses": {
          "200": {
            "description": "OK"
          },
          "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."
          }
        },
        "description": "Compatibility reference for existing integrations. Parse CSV client-side into V3 recipients batches; CSV transport is not a separate messaging capability. Recommended V3 route: `/api/ext/v3/messageTemplates/send`.\n\nSend template messages(CSV). POST /{tenantId}/api/v1/sendTemplateMessageCSV.\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": "compatibility-link-only",
          "recommendedPath": "/api/ext/v3/messageTemplates/send",
          "reason": "Parse CSV client-side into V3 recipients batches; CSV transport is not a separate messaging capability."
        },
        "x-internal": true
      }
    }
  },
  "components": {
    "securitySchemes": {
      "BearerAuth": {
        "type": "http",
        "scheme": "bearer",
        "description": "API token from your WATI Dashboard > API Settings. Pass as `Authorization: Bearer <token>`."
      }
    }
  },
  "security": [
    {
      "BearerAuth": []
    }
  ]
}
```