Skip to Content

Webhooks

Inbound platform traffic hits:

{PUBLIC_WEBHOOK_URL}/webhooks/{organization_id}/{platform}/{channel_id}

Self-host deployments use organization_id = default. Cloud tenants use the org UUID from the control plane.

MethodPlatformsPurpose
GETwhatsapp, messengerMeta verification challenge
POSTallEvent / interaction delivery

Supported {platform} values: telegram, slack, teams, discord, gchat, whatsapp, messenger.

Behavior notes

  • Telegram — Greenlight calls setWebhook when PUBLIC_WEBHOOK_URL is set; otherwise long polling
  • Slack — configure Events API Request URL in the Slack app
  • Teams — Azure Bot messaging endpoint
  • Discord — Interactions Endpoint URL; Gateway listener starts when public URL is set
  • Google Chat — App URL (+ Pub/Sub if used)
  • WhatsApp / Messenger — Meta Callback URL; verify_token must match credentials

Webhook routes live at /webhooks/... (not under /v1). They are not protected by X-API-Key — platform signing and verify tokens provide authenticity. Agent API routes under /v1 are a separate surface.

See each platform guide for portal steps.