360dialog

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.

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"] ] } } ] }

Delete a WhatsApp message template by its internal template ID.

Get balance for an account.

Get a channel's (a.k.a. phone number) WhatsApp profile.

Get a documentation page from the 360Dialog client documentation at https://docs.360dialog.com/docs. Fetch the full markdown content of a specific documentation page from Client Documentation. Use this when you have a page URL and want to read its content. Accepts full URLs (e.g. https://docs.360dialog.com/docs/getting-started). Since searchDocumentation returns partial content, use getPage to retrieve the complete page when you need more details. The content includes links you can follow to navigate to related pages.

Get the user's company's details from 360Dialog.

Get invoices for an account.

Get a phone number's status on whether a number is live, what type of messages it can send today, and suggestions for what's next.

A live number can send free-form replies inside the 24-hour customer service window immediately (meaning if someone messages the number, the user can respond to the message using the API). Template messages are separately blocked until Meta reviews a submitted template (template reviews take up to 48 hours.)

Lack of business verification is not a blocker. Unverified businesses can only send 250 templates to unique users per 24 hours.

Get currently logged in user's information in 360Dialog. You will get:

• user's name,

• user's email address,

• partner name,

• user's permissions in 360Dialog Hub,

• user's roles

Get the full guide for one skill returned by 'list_skills', as markdown.

Sending messaging templates in WhatsApp API / 360Dialog API requires a JSON body in the API request.

The API request can be hard to form, as the body must declare in JSON what each parameter in the JSON should be filled as.

This tool creates a valid example JSON body that the user can later modify before sending the template to WhatsApp users.

It is recommended that you use this tool after creating a template, or after the user asks how to send a template. Display the JSON result of this tool.

Get a channel's (a.k.a. phone number's) webhook URL, and check if the optional webhook headers are set.

Webhook headers are optional. They can be set using the 'set_webhook' tool, which also sets the webhook URL. When webhook headers are set, 360Dialog will send webhooks to the channel's webhook URL and add the specified headers.

This helps only authenticated requests pass through app firewalls, if the user has any.

Example:

If webhook URL is https://foo.com/webhook, and webhook headers are set to {"x-360dialog-webhook-security": "RANDOM-STRING"}, the webhook URL will receive POST requests like this:

POST https://foo.com/webhook HEADERS x-360dialog-webhook-security: RANDOM-STRING

Find a channel by passing in an identifier.

A channel is a phone number. By calling this tool you retrieve information about the phone number/channel in 360Dialog.

Results are paginated; use the 'page' and 'size' arguments to page through results if there are more than fit in a single page.

Returns: If not found, returns "Not found". If found, returns information of channels, like WABA ID, client ID, channel ID, and app ID, along with the current page, total pages, and total count.

List the 360Dialog skills available to you.

A skill is a curated, up-to-date how-to guide for a 360Dialog process (e.g. drafting a compliant WhatsApp template, diagnosing a channel that stopped sending). Call this tool BEFORE answering any "how do I..." question about 360Dialog products or processes - it tells you which skills exist and when to use them. Once you find a match, call 'get_skill' with its 'name' to read the full guide.

List templates for a WABA (WhatsApp Business Account). If you do not have a waba_account_id ending in 'WA' (case-insensitive), run the 'list_channels' tool first.

List users for the selected account, including their roles and creation timestamps.

Request an OTP code.

Sometimes OTP is needed to complete invoking a tool. When tool invocation fails due to OTP reasons, you will be notified in the tool response, and be asked to rqeuest an OTP code.

Only call after a tool call fails due to OTP.

Complete a phone number's registration. This will get you the API key to use when sending messages from the 360Dialog sandbox phone number to the user's registered phone number.

Set webhook for the channel on 360Dialog sandbox. Optional.

Get configured webhook for the channel on 360Dialog sandbox.

List webhook events received. This will show received messages from the user, and status of messages sent from the sandbox account.

Register the user's phone number on the 360Dialog sandbox. Upon registration, the user can send messages to this phone number from the 360Dialog sandbox account on WhatsApp.

The user will be given a link to complete registration. When this link is used, they will send a verification code to 360Dialog sandbox phone number on WhatsApp. They can click the link, or alternatively scan the QR code.

Send a message on the 360Dialog sandbox. Messages can only be sent to the user's phone number that was used during sandbox registration.

The payload must be a JSON string matching the WhatsApp messages endpoint body.

Interactive message example: use this only when there is an active conversation window, which lasts 24 hours since the customer's last message.

{ "messaging_product": "whatsapp", "to": "{{recipient_phone_number}}", "type": "text", "text": { "body": "{{message_body}}" } }

Template message example: use this when there is no active conversation window, or when sending an approved template message. You can only send the 'marketing_message' template.

{ "messaging_product": "whatsapp", "to": "{{recipient_phone_number}}", "type": "template", "template": { "name": "marketing_message", "language": { "policy": "deterministic", "code": "en" }, "components": [ { "type": "header", "parameters": [ { "type": "image", "image": { "link": "https://placehold.co/600x315/34D399/FFFFFF/png?text=Summer+Sale!" } } ] } ] } }

Search the 360Dialog client documentation at https://docs.360dialog.com/docs. Search across the documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Client Documentation, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages.

Submit a new display name for this channel (a.k.a. phone number.)

Calling this tool will submit a display name request to Meta. Meta takes up to 48 hours to review the submitted display name. The display name may be rejected if it does not comply with display name guidelines.

The user will receive an email when their display name review is complete.

When this tool is called, the user may be prompted by 360Dialog for an OTP code delivered to their email address.

Set a channel's (a.k.a. phone number's) webhook URL and optionally webhook headers.

Show a preview of a given template to the user.

Get the link that lets the user connect a WhatsApp phone number in 360Dialog, plus what to tell them beforehand.

This hands over 360Dialog's own onboarding page. The user clicks through Embedded Signup themselves; this tool cannot do it for them.

The user must be signed in to 360Dialog Hub already, or the link sends them to login first and loses the destination. Tell them to make sure they're signed in first.

The link given by this tool may not work if the user's 360Dialog client account is under a partner-paid channel. Make them aware of this.

Returns the client's current channel IDs for future reference on recognizing which phone number was newly added.

Get the link that lets the user add their credit card to their account.

If this client was created through assistant-led onboarding and still has no company name or country on file, the payment page is kept behind a company details form instead. In that case this tool does not return the payment link; it says to call 'update_company_details' first and try again.

The user must be signed in to 360Dialog Hub, or the link sends them to login first and loses the destination. The user enters the card themselves; this tool cannot do it for them.

Returns the URL where a user can create a 360Dialog account. Only relevant if the user has not created a 360Dialog account yet.

Test if a channel's (a.k.a. phone number's) webhook URL is functional.

A total of 32 test cases will be run by sending sample POST requests to the user's webhook URL. During this test, the user may see 32 requests being made to their webhook server.

Returns the test's results, showing which cases failed, and which succeeded.

Update the WhatsApp profile for this channel (a.k.a. phone number.)

The user may be prompted by 360Dialog for an OTP code delivered to their email address. Make them aware of the OTP requirement.

Set the user's company's details on 360Dialog. This change does not affect Meta; only records on 360Dialog are affected by the update.

Before calling this tool, make sure to:

1. Check if the get_company_details tool returns the correct company information already.

2. Check with the user if they want to change their company details in 360Dialog.

3. Get the user's approval/confirmation.

Verify the 6-digit OTP code from the user. Doing so will automatically replay the blocked tool call that required verification.

Wait for a server-side onboarding step to finish, then report back.

Embedded Signup and payment setup finish in the person's browser. This tool polls the hub every 5 seconds for up to 45 seconds and returns one of:

• "done": The step finished.

• "pending": Still not finished. Call this tool again to keep waiting.

• "failed": There was an error.

'channel_id' and 'phone_number' are returned back once a channel is found so you can pass 'phone_number' into the next call once you have it. When 'phone_number' is omitted, 'candidates' lists the client's most recently created channels - check it if you're unsure the right number was picked (e.g. two users connecting numbers on the same 360Dialog client account).

Only use this for the short waits during onboarding. This tool is NOT suitable for display name approval, WABA approval, or business verification scenarios, as they take days, not seconds.