Agent

Connect a Telegram channel (notification-channel-routing-telegram, v1.126)

operator_passkey assurance AND a verified contact email (bindings are addressed to the verified email). operator_passkey is satisfied by the wallet contact's passkey binding OR by a passkey-fresh, same-client control-plane session sent as Authorization: Bearer beside SIGN-IN-WITH-X, whose principal holds the contact's verified email (one person, one passkey). Creates a pending binding and returns a single-use, 15-minute deep link for a dedicated customer-facing notification bot (never the internal ops bot); the binding activates when the owner taps the link in Telegram and the bot's inbound update resolves the code. No bot token or credential is ever asked for or returned. 503s until the platform's Telegram notification bot is provisioned (docs/runbooks/telegram-notify-bot.md).

post/agent/v1/notifications/channels/telegram

Request

  • Base URL: https://api.run402.com
  • URL: https://api.run402.com/agent/v1/notifications/channels/telegram
  • Auth: API key in header SIGN-IN-WITH-X

Headers

SIGN-IN-WITH-Xstring required

SIWX auth header — base64-encoded JSON payload containing a signed CAIP-122 (EIP-4361) message. See https://docs.x402.org/extensions/sign-in-with-x.

Request body

labelstring

Optional human name for this chat, e.g. "kysigned prod".

Response

Pending binding created

binding_idstring uuid
status'pending'
connect_urlstring

t.me/<bot>?start=<code> — private chat, 15-minute single-use code.

connect_group_urlstring

t.me/<bot>?startgroup=<code> — same code, group chat.

code_expires_atstring date-time
labelstring nullable

Changes

No recorded changes to this operation across all 1 revision of this API.