Reference

API Explorer

The entire platform API, rendered live from our OpenAPI spec. Click any endpoint to see its parameters and try a request directly from the browser.

Spec source
Rendered from …. If you prefer a flat list, see the static reference.
Messaging channels: ingress & management
Inbound Telegram and WhatsApp messages are handled by dedicated routes — provider-verified, no user credential required. See the Channels overview for setup. The endpoints (also visible below):
  • POST /api/ingress/telegram/{integration_id} — secret-token verified
  • GET /api/ingress/whatsapp/{integration_id} — hub.challenge handshake
  • POST /api/ingress/whatsapp/{integration_id} — HMAC-SHA256 verified
  • GET /api/messaging-channels — list channels (X-API-Key or session)
  • POST /api/messaging-channels — create Telegram or WhatsApp channel
  • GET /api/messaging-channels/{id} — fetch one
  • PATCH /api/messaging-channels/{id} — rotate secrets, toggle auto-reply
  • DELETE /api/messaging-channels/{id} — remove a channel
  • POST /api/messaging-channels/{id}/register-telegram-webhook — helper that calls Telegram's setWebhook

Loading API Explorer…