AsyncAPI channel · Udesk
· Udesk Event Callbacks (Webhooks)
event-callback
Open API v2 event callbacks — one POST per event, body {action, message}.
Channel address
event-callback
Operations
subscribe
receiveUdeskEvent
Receive a Udesk event callback
Messages
Customer_create
Customer created
Content-Type:
Customer_update
Customer updated (id + changes diff map)
Content-Type:
Customer_destroy
Customer deleted
Content-Type:
Organization_create
Customer organization created
Content-Type:
Organization_update
Customer organization updated (id + changes diff map)
Content-Type:
Organization_destroy
Customer organization deleted
Content-Type:
ImSubSession_create
IM session created (includes im_sub_session_log)
Content-Type:
ImSubSession_close
IM session closed (session log + full chat transcript im_log_infos)
Content-Type:
ShutQueue_create
Customer abandoned the IM queue
Content-Type:
AgentNote_update
Business record updated after IM session / CC call close
Content-Type:
ImSurveyVote_create
Satisfaction survey first saved
Content-Type:
UserGroup_create
Agent group created
Content-Type:
UserGroup_update
Agent group renamed or membership changed
Content-Type:
UserGroup_destroy
Agent group deleted
Content-Type:
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.
Work with this as data
Every channel here is available over the APIs.io API and to AI agents over MCP.