360dialog
v2.2.1Manage WhatsApp Business accounts on 360Dialog: channels, templates, sandbox, inbox, and more.
Endpoint health
online- Last checked
- 11/20/2026, 7:18:30 AM
- Latency
- 358 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.360dialog%2Fmcp
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.360dialog/mcp": {
"url": "https://mcp.360dialog.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
Check number eligibility
check_number_eligibility
Check whether a phone number can be onboarded for this client before handing over the onboarding link. This tool only checks 360Dialog's own database and this client's channel quota. It does not ask WhatsApp/Meta anything, so a number already active on WhatsApp elsewhere (including the personal app) can still come back eligible here.
Schema valid · SHA-256 942c0fd57a48…
View input schema
{ "type": "object", "properties": { "phone_number": { "description": "The phone number to check", "format": "phone", "type": "string" }, "check_coex": { "default": false, "description": "Set to true if the phone number to check is currently on the WhatsApp Business app (not to be confused with the normal, personal, WhatsApp app.) WhatsApp Business app numbers can be onboarded to the API as well using WhatsApp Coexistence", "type": "boolean" } }, "required": [ "phone_number" ], "additionalProperties": false }Create template
create_template
Use this tool to create a WhatsApp message template. For this tool's 'template_json' property, pass a JSON matching this shape: { "name": string, "language": string, "category": "MARKETING" | "AUTHENTICATION" | "UTILITY", "components": Component[], } General rules: - name must be lowercase snake_case. - category must be uppercase. - language must be a WhatsApp locale code such as "en_US", "tr", "es", "pt_BR". - Only include fields supported by the component variant. - Do not include null fields. - Components should normally be ordered as: 1. header, if any 2. body 3. footer, if any 4. buttons, if any - A template can have at most one header, one body, one footer, and one buttons component. - BODY is required unless the user is clearly creating a special authentication template handled elsewhere. - HEADER and FOOTER are optional. - BUTTONS are optional. Component variants: 1. Text header without variables { "type": "HEADER", "format": "text", "text": "Your order update" } Use this when the header is plain text. 2. Text header with variables { "type": "HEADER", "format": "TEXT", "text": "Hi {{1}}", "example": { "header_text": ["Alice"] } } Rules: - Text header supports template variables. - If text contains variables, include example.header_text. - The example array must contain sample values in the same order as the variables appear. - For named parameters, the placeholder names appear in text, but the examples are still values. 3. Image header { "type": "HEADER", "format": "IMAGE", "example": { "header_handle": ["https://example.com/sample-image.jpg"] } } Use this when the template header should contain an image. The example should be a sample image handle or URL when available. 4. Video header { "type": "HEADER", "format": "VIDEO", "example": { "header_handle": ["https://example.com/sample-video.mp4"] } } Use this when the template header should contain a video. The example should be a sample video handle or URL when available. 5. Document header { "type": "HEADER", "format": "DOCUMENT", "example": { "header_handle": ["https://example.com/sample-document.pdf"] } } Use this when the template header should contain a document. The example should be a sample document handle or URL when available. 6. Location header { "type": "HEADER", "format": "LOCATION" } Use this when the template should display a location/map header. Important: - For template creation, LOCATION is only the header format. - Do not put latitude, longitude, address, or name in the template creation component. - The actual location values are supplied later when sending the approved template, not when creating the template. 7. Body without variables { "type": "BODY", "text": "Your order has shipped and is on the way." } Use this for the main message text. 8. Body with variables { "type": "BODY", "text": "Hi {{1}}, your order {{2}} has shipped.", "example": { "body_text": [ ["Alice", "ORD-12345"] ] } } Rules: - If body text contains variables, include example.body_text. - body_text is an array containing one array of sample values. - The inner array values must match the variables in order of appearance. - Use placeholders like {{1}}, {{2}}. 9. Footer { "type": "FOOTER", "text": "Reply STOP to unsubscribe." } Rules: - Footer is plain text only. - Do not use variables in footer text. 10. Buttons wrapper { "type": "BUTTONS", "buttons": [ Button ] } Rules: - Buttons must be inside a single component whose type is "BUTTONS". - Do not place button objects directly in components. - Button text should be short and action-oriented. Button variants: A. Quick reply button { "type": "QUICK_REPLY", "text": "Confirm" } Use when the user should tap a predefined reply. B. Phone number button { "type": "PHONE_NUMBER", "text": "Call us", "phone_number": "+15551234567" } Use when the user should call a business phone number. phone_number must include country code. C. Static URL button { "type": "URL", "text": "View order", "url": "https://example.com/orders" } Use when the button always opens the same URL. D. Dynamic URL button { "type": "URL", "text": "View order", "url": "https://example.com/orders/{{1}}", "example": ["ORD-12345"] } Rules: - Use this when the final URL path or query contains a variable. - The example array contains the sample value for the dynamic URL part. E. Copy code button { "type": "COPY_CODE", "example": "SAVE20" } Use for coupon or promo-code templates. The button copies the provided code when the template is sent. G. OTP button { "type": "OTP", "otp_type": "COPY_CODE", "text": "Copy code" } For one-tap OTP: { "type": "OTP", "otp_type": "ONE_TAP", "text": "Copy code", "autofill_text": "Autofill", "package_name": "com.example.app", "signature_hash": "abc123" } Rules: - Use OTP buttons only for authentication templates - category should be "AUTHENTICATION". Authentication templates can only be created for WABAs that have a 2,000 messaging limit or above. - Do not use marketing or utility wording in authentication templates. Examples: Utility order update with named parameters: { "name": "order_shipped_update", "language": "en_US", "category": "UTILITY", "components": [ { "type": "HEADER", "format": "TEXT", "text": "Order {{1}} update", "example": { "header_text": [["ORD-12345"]] } }, { "type": "BODY", "text": "Hi {{1}}, your order has shipped and should arrive by {{2}}.", "example": { "body_text": [ ["Alice", "Friday"] ] } }, { "type": "FOOTER", "text": "Thank you for shopping with us." }, { "type": "BUTTONS", "buttons": [ { "type": "URL", "text": "Track order", "url": "https://example.com/orders/{{1}}", "example": ["ORD-12345"] } ] } ] } Utility store location template: { "name": "store_location_info", "language": "en_US", "category": "UTILITY", "components": [ { "type": "HEADER", "format": "location" }, { "type": "BODY", "text": "Hi {{1}}, here is the location of our {{2}} store.", "example": { "body_text": [ ["Alice", "Downtown"] ] } } ] }
Connections
streamable-http
https://mcp.360dialog.com/mcp