Activate a connector
Revalidates the stored Telegram credentials and registers the provider webhook. Use this to retry a connector left in an error state or rotate its key. API-key authentication with every listed scope is required; session authentication is rejected, and the new key must belong to the connector’s original user or service-account principal so existing conversations keep the same owner.
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.
Response
Activated connector.
agent.connector telegram Connector lifecycle status, such as provisioning, activating, active, deleting, or error.
The Telegram bot user ID.
The Telegram bot username when one is available.
Whether encrypted provider credentials are stored for this connector.