Events - Returning.AI-dev

Outgoing webhooks notify your HTTPS endpoint when community events fire. Incoming webhooks let an external system call Returning.AI to update fields, coins/XP, or post as a bot.

Configure these in Community Settings → Integrations → Webhooks. There is no public HTTP API that lists webhook subscriptions.

WARNING

Register only https:// callback URLs. Keep any webhook secret on the server. Do not put community API keys in the browser.

Outgoing

Create an outgoing webhook, set the request URL and format (JSON or XML), subscribe to events, and optionally enable encryption.

Delivery history is under Recent deliveries.

Start at Outgoing webhooks.

Incoming

Create an incoming webhook, optionally set an API key and encryption, choose Chat or User fields, then copy the incoming URL. Trigger it once, then catch so you can map payload fields.

History states: Success, Failed (reason in histories), Pending (escalate if a delivery stays pending).

Start at Incoming webhooks.

When to use HTTP APIs instead

Member lookup, filter, and manage → User directory

Channel messages → Monitor and respond

Store fulfillment → Store catalog to redemptions

Webhooks

Outgoing#

Incoming#

When to use HTTP APIs instead#

Outgoing

Incoming

When to use HTTP APIs instead