Skip to main content
Webhooks let bots call external APIs during conversations — for example, checking order status, submitting a form, or syncing data. All endpoints require authentication.

Endpoints

Webhooks are managed per-bot. See Bots — Bot Webhooks.
GET    /api/bots/:id/webhooks
POST   /api/bots/:id/webhooks
PATCH  /api/bots/:id/webhooks/:webhookId

Create a Webhook

POST /api/bots/:id/webhooks
Body
FieldTypeRequiredDescription
namestringYesLabel (e.g., “Check Order Status”)
urlstringYesFull API endpoint URL
methodstringYesGET, POST, PUT, PATCH, DELETE
descriptionstringYesWhat it does — the AI reads this
headersobjectNoHTTP headers as JSON {"Authorization": "Bearer TOKEN"}
queryParamsobjectNoURL query parameters as JSON
jsonDataobjectNoRequest body for POST/PUT
activebooleanNoDefault true
parametersarrayNoDynamic parameters (see below)

Parameter object

FieldTypeDescription
namestringParameter name
dataTypestringstring, number, date, datetime
typestringquery_param, post_data, path_param
sourcestringby_ai (bot fills it) or fixed
valuestringFixed value (if source is fixed)

Incoming Webhooks (platform webhooks)

These are system-level endpoints that receive events from external providers:
EndpointProvider
POST /api/webhooks/gupshup/incoming_msgGupshup — incoming WhatsApp messages
POST /api/webhooks/gupshup/message-eventsGupshup — delivery/read receipts
GET/POST /api/webhook/facebookFacebook/Meta
POST /api/webhook/wasimpleWasimple
POST /api/stripe-webhookStripe billing events
These endpoints are called by external providers, not by your code. Configure the URLs in your respective provider dashboards.