Chat API for WhatsApp MCP integration for AI agents.
Connect AI agents to Chat API for WhatsApp through 8 structured actions, including get settings, send file by url, and test api key. Review authentication, i…
- ACTION CONTRACTS
- 8
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Chat API for WhatsApp integration exposes
The Chat API for WhatsApp Agent App exposes 8 provider-backed actions for communication and developer tools work. Its current contract lets an authorized agent get the current webhook, notification, video upload, and proxy settings, send a file using a public url to an existing chat api chat id or to a phone number, and validate the connected chat api token and instance id, returning the current instance status. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Chat API for WhatsApp account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Chat API for WhatsApp capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_settingsREADGet the current webhook, notification, video upload, and proxy settings.
send_file_by_urlWRITESend a file using a public URL to an existing Chat API chat ID or to a phone number.
INPUTS: chatId / phone / fileUrl / filename / caption
test_api_keyREVIEWValidate the connected Chat API token and instance ID, returning the current instance status.
get_statusREADGet the current Chat API WhatsApp instance status and QR code payload when authorization is pending.
list_chatsREADList chats known to the connected Chat API WhatsApp instance.
list_messagesREADList incoming and outgoing messages, optionally filtered by chat ID or paged from a previous response.
INPUTS: lastMessageNumber / last / chatId
list_messages_queueREADList outbound messages currently waiting in the Chat API send queue.
send_text_messageWRITESend a text message to an existing Chat API chat ID or to a phone number.
INPUTS: chatId / phone / text
INPUT CONTRACTS
Know what the action needs before it runs.
send_file_by_url
chatIdOPTIONAL- Chat API chat ID, such as 17633123456@c.us for a private chat or 17680561234-1479621234@g.us for a group.
phoneOPTIONAL- Recipient phone number starting with the country code, without plus sign or separators.
fileUrlREQUIRED- Public HTTP or HTTPS URL of the file Chat API should send.
filenameREQUIRED- File name to show in WhatsApp, such as invoice.pdf.
captionOPTIONAL- Optional text caption to show under the file.
list_messages
lastMessageNumberOPTIONAL- The lastMessageNumber value from a previous list_messages response.
lastOPTIONAL- Whether to request the last 100 messages and ignore lastMessageNumber.
chatIdOPTIONAL- Optional Chat API chat ID to filter messages by.
send_text_message
chatIdOPTIONAL- Chat API chat ID, such as 17633123456@c.us for a private chat or 17680561234-1479621234@g.us for a group.
phoneOPTIONAL- Recipient phone number starting with the country code, without plus sign or separators.
textREQUIRED- Message text to send.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Settings
Get the current webhook, notification, video upload, and proxy settings. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_settingsControl Send File By Url
Send a file using a public URL to an existing Chat API chat ID or to a phone number. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
send_file_by_urlVerify with Get Status
Get the current Chat API WhatsApp instance status and QR code payload when authorization is pending. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_statusSAFETY BOUNDARY
Operate Chat API for WhatsApp with explicit limits
- Authorize Chat API for WhatsApp with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Chat API for WhatsApp rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Chat API for WhatsApp task completed successfully.
CONNECTION MODEL
API key
Chat API token sent as the token query parameter. Sign in to Chat API and copy the token for your instance from the API access dashboard: https://chat-api.com/en/get-api.html#login.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Chat API for WhatsApp.