Skip to main content
POST
Connect the claimed Telegram group

Authorizations

X-API-Key
string
header
required

A compute API key (x402c_...). Mint one in the dashboard under Settings -> API Keys. This is the ONLY auth /pods/v1/* accepts - wallet signatures are bound to method+path+body and do not survive the internal hop, so signature callers must use the dashboard routes instead. Two extra scopes gate the dangerous powers: pods:wallet:write (pod wallet money, backup passphrase) and pods:control:write (connectors, full-power control socket).

Path Parameters

id
string<uuid>
required

Pod id, as returned by create/list.

Body

application/json
require_mention
boolean
default:true

Default true: a freshly connected room should not have the agent answering every message until the owner decides that is what they want.

prompt
string

Optional per-group instruction.

Response

Connected. The pod applies it on its next check-in.

channel
object