Integration

360dialog WhatsApp API integration

360dialog is an official WhatsApp Business Platform provider. An agent can send WhatsApp messages (text, media, location, contacts, interactive, reactions, approved templates and marketing templates) from the business number, mark messages read with a typing indicator, upload and fetch media, create, edit, archive and compare message templates, build and publish WhatsApp Flows, manage WhatsApp groups and join requests, block users, read the number's health, business profile, username and calling settings, set the webhook URLs that receive inbound messages and statuses, read marketing reach estimates, ad insights and conversion datasets, and send RCS messages through 360dialog's RCS senders and templates. Every call acts on the WhatsApp number the API key belongs to. Not included: call answering (it needs a live WebRTC media session), custom webhook headers (set them in the 360dialog Hub), the deprecated v1 template routes, duplicate alternative routes, and the payments and Meta Business Agent APIs. Authentication is the number's 360dialog API key, generated in the 360dialog Hub (API Settings of the channel) and sent in the D360-API-KEY header; generating a new key revokes the previous ones.

Connect 360dialog WhatsApp API How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in 360dialog WhatsApp API.Built from the 102 360dialog WhatsApp API tools below, on the connection you add once.

What you can do with 360dialog WhatsApp API

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Message template, 8 operations

archive_message_templatesArchive message templatesPOSTAgents: ask firstArchives approved or rejected message templates; archived templates are deleted after 28 days unless unarchived. Answers the archived ids and the failures.
compare_message_templatesCompare message templatesGETAgents: ask firstCompares two templates of the account by block rate, send volume and top block reason over a 7, 30, 60 or 90 day window; both must have been sent at least 1,000 times in it.
create_message_templateCreate message templatePOSTAgents: ask firstCreates a WhatsApp message template and submits it to Meta review (status PENDING, or REJECTED for a wrong category); it can be sent once APPROVED. Can also copy a template from the template library. Returns id, status, category.
delete_message_templatesDelete message templatesDELETEAgents: ask firstDeletes message templates: by name (every language), by name plus hsm_id (one language) or by hsm_ids (up to 100). A deleted approved name cannot be reused for 30 days. Answers success.
get_message_templateGet message templateGETAgents: ask firstReturns one message template with its name, language, category, status, components, quality score, rejection reason and bid settings.
list_message_templatesList message templatesGETAgents: ask firstLists the account's message templates with their id, name, language, category, status, components, quality score and rejection reason, page by page with the after and before cursors.
unarchive_message_templatesUnarchive message templatesPOSTAgents: ask firstRestores archived message templates within their 28-day window to their previous status (APPROVED when unknown) and resets their inactivity clock. Answers the restored ids and the failures.
update_message_templateUpdate message templatePOSTAgents: ask firstEdits an approved or rejected message template; it goes back to Meta review. Send the fields to change. Answers success.

Flow, 7 operations

create_flowCreate flowPOSTAgents: ask firstCreates a WhatsApp Flow as a draft (or published when publish is true and flow_json is given). Send the screens in flow_json or later with upload_flow_json. Returns the Flow id and any validation errors.
delete_flowDelete flowDELETEAgents: ask firstDeletes a Flow. Only a Flow still in DRAFT status can be deleted; use deprecate_flow for a published one.
deprecate_flowDeprecate flowPOSTAgents: ask firstDeprecates a published Flow: it can no longer be sent or opened, and this cannot be undone. Answers success.
get_flowGet flowGETAgents: ask firstReturns one Flow: name, categories, status, validation errors, JSON and data API versions and endpoint URI. Ask for the preview field in fields to also get a shareable preview link.
list_flowsList flowsGETAgents: ask firstLists the WhatsApp Flows of the account with their id, name, categories, status and unresolved validation errors, page by page with the after and before cursors.
publish_flowPublish flowPOSTAgents: ask firstPublishes a draft Flow so it can be sent to users. A published Flow can no longer be edited, only deprecated. Answers success.
update_flowUpdate flowPOSTAgents: ask firstUpdates a draft Flow's name, categories or endpoint URI. Fields left out keep their current value. Answers success.

Rcs template, 6 operations

create_rcs_templateCreate rcs templatePOSTAgents: ask firstCreates an RCS template for a sender and submits it for approval with the chosen providers; once approved it is sent as PROVIDER_TEMPLATE content with send_rcs_messages.
delete_rcs_templateDelete rcs templateDELETEAgents: ask firstDeletes an RCS template; messages sent with it afterwards are rejected.
get_rcs_templateGet rcs templateGETAgents: ask firstReturns an RCS template with its content (text, suggestions, cards or PDF) and its overall approval status.
list_rcs_templatesList rcs templatesGETAgents: ask firstLists the RCS templates of a sender (name, type, status, last update) without their content, optionally only those with one status.
register_rcs_template_providersRegister rcs template providersPATCHAgents: ask firstSubmits an existing RCS template to more providers, for example after the sender launched with a new one. List only providers it is not registered with yet.
update_rcs_templateUpdate rcs templatePUTAgents: ask firstReplaces the content of a PENDING, REJECTED or SUSPENDED RCS template (not an APPROVED one); it goes through approval again. Send the whole new content: type plus its fields.

Group, 5 operations

create_groupCreate groupPOSTAgents: ask firstCreates a WhatsApp group owned by the business number and returns its id. Participants cannot be added directly: send them the invite link from get_group_invite_link.
delete_groupDelete groupDELETEAgents: ask firstDeletes a group and removes every participant, the business included. This cannot be undone.
get_groupGet groupGETAgents: ask firstReturns a group's metadata. Name the fields to return (subject, description, participants, join_approval_mode, total_participant_count...); without fields only the id comes back. Participants are personal data.
list_groupsList groupsGETAgents: ask firstLists the active WhatsApp groups of the business number (id, subject, creation time), 25 per page by default, with the after and before cursors.
update_group_settingsUpdate group settingsPOSTAgents: ask firstChanges a group's subject or description. Fields left out keep their current value. Answers success.

Conversion dataset, 4 operations

create_conversion_datasetCreate conversion datasetPOSTAgents: ask firstCreates the Conversions API dataset of a channel account (WABA, Facebook Page or Instagram user ID), or returns the existing one, with its id and name.
create_waba_datasetCreate waba datasetPOSTAgents: ask firstCreates the Conversions API dataset of the account's WhatsApp Business Account, or returns the existing one, with its id and name. Use create_conversion_dataset for Messenger or Instagram.
get_conversion_datasetGet conversion datasetGETAgents: ask firstReturns the Conversions API dataset (id and name) of a channel account: a WhatsApp Business Account ID, a Facebook Page ID or an Instagram user ID.
get_waba_datasetGet waba datasetGETAgents: ask firstReturns the Conversions API dataset (id and name) linked to the account's WhatsApp Business Account, which the API key determines. Use get_conversion_dataset for a Messenger or Instagram channel.

Blocked user, 3 operations

block_usersBlock usersPOSTAgents: ask firstBlocks WhatsApp users: they can no longer contact the business or see it online, and the business cannot message them. The answer lists the users blocked and the ones that failed.
list_blocked_usersList blocked usersGETAgents: ask firstLists the WhatsApp users blocked on the business number (their phone number and WhatsApp ID, personal data), page by page with the after and before cursors.
unblock_usersUnblock usersDELETEAgents: ask firstUnblocks WhatsApp users so they can contact the business again. Pass the users in block_users; the answer lists the users processed and the ones that failed with their errors.

Business username, 3 operations

adopt_business_usernameAdopt business usernamePOSTAgents: ask firstAdopts or changes the business username of the number. On success its status is approved (visible once the feature is rolled out) or reserved (approved but not yet visible).
delete_business_usernameDelete business usernameDELETEAgents: ask firstDeletes the business username of the number (the handle users can search for). Answers success.
get_business_usernameGet business usernameGETAgents: ask firstReturns the business username of the number (a handle for discoverability that does not hide the phone number) and its status.

Join request, 3 operations

approve_join_requestsApprove join requestsPOSTAgents: ask firstApproves pending join requests: the users become group participants. The answer lists the requests approved and the ones that failed with their errors.
list_join_requestsList join requestsGETAgents: ask firstLists the pending join requests of a group: request id, the requester's WhatsApp ID (personal data) and the request time.
reject_join_requestsReject join requestsDELETEAgents: ask firstRejects pending join requests of a group. The answer lists the requests rejected and the ones that failed with their errors.

Media, 3 operations

delete_mediaDelete mediaDELETEAgents: ask firstDeletes an uploaded media file from Meta's storage; its media id can no longer be sent. Answers success.
download_mediaDownload mediaGETAgents: ask firstDownloads a media file and returns it as a file. Pass mid, ext and hash from the query string of the url that get_media_url returned (valid 5 minutes). Inbound media can hold personal data.
upload_mediaUpload mediaPOSTAgents: ask firstUploads a media file (image, video, audio, document or sticker) and returns its media id, to send it with send_message. Files are kept for 30 days after last use; at most 25 uploads per second per number.

Rcs sender, 3 operations

create_rcs_senderCreate rcs senderPOSTAgents: ask firstCreates an RCS sender (the brand profile recipients see) for the number; it starts PENDING, check it with get_rcs_sender. Once READY_FOR_TESTING it can message its approved test numbers.
get_rcs_senderGet rcs senderGETAgents: ask firstReturns an RCS sender of the number with its brand profile (display name, description, color, logo, banner, contacts, privacy and terms URLs), use case, billing category and status.
list_rcs_sendersList rcs sendersGETAgents: ask firstLists the RCS senders of the number with their name and creation time.

Webhook destination, 3 operations

add_multi_webhook_destinationsAdd multi webhook destinationsPUTAgents: ask firstAdds webhook destinations ({name, url}) to the enabled multi-webhook configuration; names must be unique and the total cannot pass the configured maximum. Events also go to them. Sends no custom headers.
delete_multi_webhook_destinationDelete multi webhook destinationDELETEAgents: ask firstDeletes one additional webhook destination by its name; multi-webhook must be enabled. Answers a message.
update_multi_webhook_destinationUpdate multi webhook destinationPATCHAgents: ask firstChanges the URL of an additional webhook destination, found by its name; multi-webhook must be enabled. Events then also go to the new URL. Sends no custom headers: if the destination needs them, do not use this tool.

Business compliance info, 2 operations

get_business_compliance_infoGet business compliance infoGETAgents: ask firstReturns the business compliance details stored for the WhatsApp Business Account: legal entity name and type, registration flag, and the customer care and grievance officer contacts (personal data).
update_business_compliance_infoUpdate business compliance infoPOSTAgents: ask firstSaves the business compliance details Meta displays for the business: legal entity name and type, whether it is registered, and the customer care and grievance officer contacts. Answers success.

Business profile, 2 operations

get_business_profileGet business profileGETAgents: ask firstReturns the number's WhatsApp business profile: about text, address, description, contact email, industry (vertical), websites and profile picture URL.
update_business_profileUpdate business profilePOSTAgents: ask firstUpdates the number's WhatsApp business profile shown to users. Fields left out keep their value. For a new picture, get a handle with create_upload_session and upload_file_to_session first. Answers success.

Business public key, 2 operations

get_business_public_keyGet business public keyGETAgents: ask firstReturns the business public key of the number (used to encrypt Flow payloads and data channel requests) and its signature verification status.
set_business_public_keySet business public keyPOSTAgents: ask firstUploads the business public key of the number (RSA, PEM format) used to encrypt Flow payloads; only one key is active, so it replaces the previous one. Answers success.

Calling settings, 2 operations

get_calling_settingsGet calling settingsGETAgents: ask firstReturns the number's WhatsApp calling settings: calling on or off, call icon visibility, call hours, callback permission, SIP status and servers, SRTP key exchange, plus payload encryption and storage settings.
update_calling_settingsUpdate calling settingsPOSTAgents: ask firstChanges the number's WhatsApp calling settings. Send one feature setting per call inside calling (status, call_icon_visibility, video, sip or srtp_key_exchange_protocol). Answers success.

Conversational automation, 2 operations

get_conversational_automationGet conversational automationGETAgents: ask firstReturns the number's conversational components: whether the welcome message is on, the commands (name and description) and the ice-breaker prompts.
set_conversational_automationSet conversational automationPOSTAgents: ask firstSets the number's conversational components shown in an empty chat: the welcome message switch, the slash commands and the ice-breaker prompts. Answers success.

Group invite link, 2 operations

get_group_invite_linkGet group invite linkGETAgents: ask firstReturns the current invite link of a group; anyone with the link can ask to join.
reset_group_invite_linkReset group invite linkPOSTAgents: ask firstResets a group's invite link: the previous link stops working and the new one is returned.

Rcs capability, 2 operations

check_rcs_capabilityCheck rcs capabilityPOSTAgents: ask firstChecks at once whether up to 500 phone numbers (ideally 1 to 10) can receive RCS messages from a sender, to choose between RCS and another channel just before sending. Use check_rcs_capability_bulk for more.
check_rcs_capability_bulkCheck rcs capability bulkPOSTAgents: ask firstStarts an RCS capability check of up to 10,000 phone numbers for a sender. The answer only confirms acceptance; each result is posted to notifyUrl, or to the number's RCS webhook when notifyUrl is left out.

Rcs test number, 2 operations

invite_rcs_test_numberInvite rcs test numberPOSTAgents: ask firstInvites a phone number to test an RCS sender before launch: the tester gets an invitation on the device to accept within 24 hours. Up to 20 invitations per sender per day and 200 in total.
list_rcs_test_numbersList rcs test numbersGETAgents: ask firstLists the test numbers of an RCS sender, newest first, with their status (whether the tester accepted the invitation; statuses can lag) and primary flag. Test numbers are personal data.

Rcs webhook config, 2 operations

get_rcs_webhook_configGet rcs webhook configGETAgents: ask firstReturns the URL that receives the number's RCS events (inbound messages, delivery and seen reports); null when none is set. Custom headers are not returned.
set_rcs_webhook_configSet rcs webhook configPUTAgents: ask firstSets the URL that receives the number's RCS events (inbound messages, delivery and seen reports for every sender); the next event goes there. This tool sends no custom headers: if your endpoint needs them, do not use it.

Template analytics, 2 operations

enable_template_analyticsEnable template analyticsPOSTAgents: ask firstTurns on template analytics for the WhatsApp Business Account, so get_template_analytics can return data. Answers success.
get_template_analyticsGet template analyticsGETAgents: ask firstReturns analytics of the account's message templates: for each template id, metrics (metric type and granularity) with data points (start and end as Unix seconds, value). The vendor documents no filter parameters.

Upload session, 2 operations

create_upload_sessionCreate upload sessionPOSTAgents: ask firstStarts a resumable upload session for a file (name, size in bytes, MIME type) and returns its id, upload:<session id>. Then send the bytes with upload_file_to_session to get a file handle.
get_upload_sessionGet upload sessionGETAgents: ask firstReturns the state of a resumable upload session: its id and file_offset, the number of bytes already received, to resume an interrupted upload from that byte.

Waba webhook config, 2 operations

get_waba_webhook_configGet waba webhook configGETAgents: ask firstReturns the WhatsApp Business Account webhook: its URL, the WABA id and the phone numbers of the account. Custom headers are not returned.
set_waba_webhook_configSet waba webhook configPOSTAgents: ask firstSets the WABA-level webhook URL, applied in 15 to 20 seconds: override_all false only to Cloud API numbers without a number webhook, true to every number. Sends no custom headers: if the endpoint needs them, set it in the 360dialog Hub instead.

Webhook config, 2 operations

get_webhook_configGet webhook configGETAgents: ask firstReturns the webhook URL of the number, which receives inbound messages and message statuses. Custom headers are not returned.
set_webhook_configSet webhook configPOSTAgents: ask firstSets the number's webhook URL for inbound messages and statuses; it must answer HTTP 200 within 5 seconds or events are retried for up to 7 days. Sends no custom headers: if the endpoint needs them (Basic Auth), set it in the 360dialog Hub instead.

Ad insight, 1 operation

get_ad_insightsGet ad insightsGETAgents: ask firstReturns Meta ads performance of an ad account, campaign, ad set or ad (impressions, reach, clicks, spend, CPC, CPM, CTR, actions), with optional date range, level, breakdowns and attribution windows.

Business username suggestion, 1 operation

list_business_username_suggestionsList business username suggestionsGETAgents: ask firstLists reserved business username suggestions for the number; a reserved username is more likely to be approved by adopt_business_username.

Call permission, 1 operation

get_call_permissionsGet call permissionsGETAgents: ask firstReturns whether the business may call a WhatsApp user: the permission status and expiry, and for each call action whether it can be performed now and its usage limits.

Contact book entry, 1 operation

delete_contact_book_entryDelete contact book entryDELETEAgents: ask firstDeletes the contact book entry of one business-scoped user ID (BSUID) on the business number. The BSUID must belong to the same business portfolio; parent BSUIDs are not supported.

Conversion event, 1 operation

send_conversion_eventsSend conversion eventsPOSTAgents: ask firstSends Conversions API events (purchases, leads...) for business messaging to a dataset, so Meta can attribute them to click-to-WhatsApp ads. Sends customer data (hashed identifiers) to Meta.

Dataset quality, 1 operation

get_dataset_qualityGet dataset qualityGETAgents: ask firstReturns quality metrics of a Conversions API dataset: event match quality score and match key feedback, event coverage, deduplication feedback, data freshness and ACR, per event name.

Flow asset, 1 operation

list_flow_assetsList flow assetsGETAgents: ask firstLists the assets attached to a Flow (its Flow JSON), each with its name, asset type and a download URL.

Flow json, 1 operation

upload_flow_jsonUpload flow jsonPOSTAgents: ask firstUploads the Flow JSON file of a draft Flow, replacing its screens. Returns the validation errors Meta found; the Flow can be published only once they are resolved.

Flow preview, 1 operation

get_flow_preview_linkGet flow preview linkGETAgents: ask firstReturns a shareable web preview link of a Flow that needs no login, with its expiry time. Set invalidate to true to revoke the previous link and get a new one.

Group participant, 1 operation

remove_group_participantsRemove group participantsDELETEAgents: ask firstRemoves participants from a group. A removed participant can no longer join through an invite link. Answers success.

Health status, 1 operation

get_health_statusGet health statusGETAgents: ask firstReturns the number's health: can_send_message is AVAILABLE, LIMITED or BLOCKED, with the errors and fixes per entity (phone number, WABA, business, app), plus its display number, verified name, quality rating and messaging tier.

Library template, 1 operation

list_template_libraryList template libraryGETAgents: ask firstLists ready-made templates from Meta's template library (name, category, topic, use case, industry, language, header, body, body parameters and buttons), usable as library_template_name in create_message_template.

Marketing message, 1 operation

send_marketing_messageSend marketing messagePOSTAgents: ask firstSends a marketing template message to one WhatsApp user through the Marketing Messages API: it reaches a real person and is billed. Returns the message id and the recipient's WhatsApp ID.

Media url, 1 operation

get_media_urlGet media urlGETAgents: ask firstReturns the metadata of a media id (MIME type, SHA-256, size) and a download URL valid for 5 minutes; download the bytes with download_media using that URL's mid, ext and hash values.

Message, 1 operation

send_messageSend messagePOSTAgents: ask firstSends a WhatsApp message to a person or group (text, media, location, contacts, interactive, reaction or approved template). It reaches real people; outside the 24-hour customer service window only a template goes through.

Message read status, 1 operation

mark_message_readMark message readPOSTAgents: ask firstMarks a received WhatsApp message as read (blue ticks). With typing_indicator it also shows the user a typing indicator until you reply or 25 seconds pass. Pass the wamid of the inbound message. Answers success.

Message sample, 1 operation

submit_message_sampleSubmit message samplePOSTAgents: ask firstSubmits a sample text or interactive message for Direct Send, so Meta can classify it and generate a matching template; submit 3 to 4 samples covering what you plan to send. Answers success and the category.

Multi webhook, 1 operation

set_multi_webhookSet multi webhookPOSTAgents: ask firstTurns multi-webhook on or off; when on, events also go to the additional destinations. Can set initial destinations ({name, url}, unique names); add more later with add_multi_webhook_destinations. Sends no custom headers.

Multi webhook config, 1 operation

get_multi_webhook_configGet multi webhook configGETAgents: ask firstReturns the additional webhook destinations of the number (name and URL) and whether multi-webhook is enabled. Their custom headers are not returned.

Rcs delivery report, 1 operation

fetch_rcs_delivery_reportsFetch rcs delivery reportsGETAgents: ask firstFetches the latest RCS delivery reports of the number. Each report is returned only once and kept 48 hours: a report already fetched never comes back, so store what you need. Recipients are personal data.

Rcs event, 1 operation

send_rcs_eventsSend rcs eventsPOSTAgents: ask firstSends RCS events to recipients: SEEN marks an inbound message read (content.messageId = its id), TYPING_INDICATOR shows you are typing. Each sender must belong to the number. Up to 100 requests per second.

Rcs log, 1 operation

list_rcs_logsList rcs logsGETAgents: ask firstLists logs of RCS messages the number sent in the last 48 hours: content, recipient (personal data), status, error and price, up to 1,000 per call; set useCursor and pass cursor.nextCursor to page.

Rcs message, 1 operation

send_rcs_messagesSend rcs messagesPOSTAgents: ask firstSends RCS messages to real phone numbers: each has a sender, destinations and one content (TEXT, FILE, CARD, CAROUSEL or PROVIDER_TEMPLATE). Accepted, not yet delivered: follow messageId with fetch_rcs_delivery_reports.

Rcs sender launch status, 1 operation

get_rcs_sender_launch_statusGet rcs sender launch statusGETAgents: ask firstReturns the launch status of an RCS sender per country and mobile network provider; once a provider is COMPLETED the sender can message all its recipients.

Rcs template provider, 1 operation

list_rcs_template_providersList rcs template providersGETAgents: ask firstLists the providers an RCS sender's templates can be registered with, optionally for one country.

Rcs template status, 1 operation

get_rcs_template_statusGet rcs template statusGETAgents: ask firstReturns the approval status of an RCS template per country and provider, with its overall status.

Reach estimate, 1 operation

get_reach_estimateGet reach estimateGETAgents: ask firstEstimates how many WhatsApp users a marketing message can reach for a country targeting, with delivery and cost bounds per bid amount (in the smallest unit of the account currency per 1,000 deliveries).

Upload session file, 1 operation

upload_file_to_sessionUpload file to sessionPOSTAgents: ask firstSends a file's bytes to a resumable upload session and returns its file handle h, used as a template header example (header_handle) or as profile_picture_handle in update_business_profile.

Use 360dialog WhatsApp API from Claude Code, Cursor or Codex

Connect 360dialog WhatsApp API in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its 360dialog WhatsApp API operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect 360dialog WhatsApp API

Create your workspace
Sign up free. Nothing to install.
Connect 360dialog WhatsApp API once
Add your 360dialog WhatsApp API connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.