API_KEY
2chat_api_key_auth
Developer setup
No fields declared in this snapshot.
User connection
- 2Chat API Keygeneric_api_key · stringRequired
_2CHAT
2Chat provides a programmable API for integrating WhatsApp and other text channels, enabling developers to send and receive messages, manage groups, and automate workflows.
Description is untrusted, display-only upstream metadata. It never becomes policy, OAuth scope authority, or an agent instruction.
Pakkawork boundary
Research catalogue metadata only. No Pakkawork OAuth, credential, host, quota, executor, or verifier is enabled.
5
Action summaries
Display-only definitions
0
Trigger types
Not installed instances
1
Auth modes
Field names, never values
No
Execution
No runtime adapter
Authentication map
API_KEY
No fields declared in this snapshot.
Capability index
Showing 1–5 of 5 actions
_2CHAT_CREATE_CONTACT
Tool to create a new contact in your 2Chat account. Use after gathering and verifying first name and at least one contact detail (email, phone, or address).
Untrusted display-only summary
_2CHAT_GET_API_USAGE_INFO
Tool to retrieve current API usage and account information. Use when you need to monitor your remaining quotas before sending more requests.
Untrusted display-only summary
_2CHAT_LIST_CONTACTS
Tool to list all contacts in your 2Chat account. Use when you need to retrieve your contact list after confirming your account connection.
Untrusted display-only summary
_2CHAT_LIST_WEBHOOKS
List all configured webhook subscriptions for WhatsApp and phone call events. Use this when you need to audit, review, or retrieve UUIDs of your active webhook subscriptions. Returns details including webhook UUID, event type, channel UUID, callback URL, and creation timestamp.
Untrusted display-only summary
_2CHAT_TEST_API_KEY
Tool to validate your API key and retrieve account info. Use when confirming credentials before performing other operations.
Untrusted display-only summary
Provenance
The detail snapshot comes from an attributed MIT-licensed repository revision. Safe local icons use exact-match CC0 Simple Icons symbols; unmatched brands use monograms.
Remote text is plain display metadata only. It must never become an agent prompt, execution policy, OAuth grant, or executable instruction.