Create a connector
Connects the agent to a Telegram bot or WhatsApp Business phone number, validates the provider credentials, and registers the agent’s webhook. WhatsApp connector support is beta. Text, photos, and gateway-supported documents can invoke the agent; inbound media additionally requires write:files. Managed outbound files require read:files, and generated images require both file scopes so their transient provider URLs can be materialized before delivery. The optional write:feedback scope enables native thumbs reaction synchronization to gateway response feedback. These conditional scopes are deliberately not part of x-required-scopes because text-only connectors do not need them. An API key with every listed scope is required; its identity tuple and current scopes are stored as a non-widening ceiling, then revalidated with mk-authentication before every connector run; session and delegated end-user contexts are rejected. The required access policy controls which provider users or chats may invoke the agent.
Authorizations
Gateway auth: send Authorization: Bearer <mka1-api-key>. For multi-user server-side integrations, you can also send X-On-Behalf-Of: <external-user-id>.
Headers
Optional external end-user identifier forwarded by the API gateway.
Path Parameters
The agent ID.
Body
- Option 1
- Option 2
Telegram connector configuration. Creating or activating a connector always discards pending Telegram updates so events from a previous bot binding cannot be delivered to this agent.
Telegram Bot API connector. Supports text, photos up to the Bot API's 20 MiB download limit, gateway-supported documents, and response feedback through native thumbs reactions.
telegram The explicit Telegram chat allowlist permitted to invoke the agent.
1 - 120Response
Connector created and activated.
agent.connector telegram, whatsapp Connector lifecycle status, such as provisioning, activating, active, deleting, or error.
The provider account ID: Telegram bot user ID or WhatsApp phone-number ID.
Provider account display name when one is available.
Arbitrary JSON value.
Whether encrypted provider credentials are stored for this connector.
Arbitrary JSON value.