AsyncAPI channel · Didomi
· Didomi Consent Webhooks
/
A single endpoint receives every subscribed event type for the organization. Event routing is done on the `type` field of the payload, not on the URL path.
Channel address
/
Operations
receive
receiveConsentWebhook
Receive a Didomi consent webhook.
Messages
event.created
A new consent event has been created.
Content-Type:
application/jsonevent.updated
An existing consent event has been updated.
Content-Type:
application/jsonevent.deleted
An existing consent event has been deleted.
Content-Type:
application/jsonuser.created
A new user has been created.
Content-Type:
application/jsonuser.updated
An existing user has been updated.
Content-Type:
application/jsonuser.deleted
An existing user has been deleted.
Content-Type:
application/jsonAbout 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.