Subscriber endpoint that receives GoCardless webhook deliveries. A
single delivery contains one or more event objects in the `events`
array (max 250). The same channel is reused for every resource type
and action - dispatch by `resource_type` + `action` in the receiver.
Event(s) for the `billing_requests` resource type.
Content-Type: application/json
CreditorEvent
Event(s) for the `creditors` resource type.
Content-Type: application/json
CustomerEvent
Event(s) for the `customers` resource type.
Content-Type: application/json
ExportEvent
Event(s) for the `exports` resource type.
Content-Type: application/json
InstalmentScheduleEvent
Event(s) for the `instalment_schedules` resource type.
Content-Type: application/json
MandateEvent
Event(s) for the `mandates` resource type.
Content-Type: application/json
OutboundPaymentEvent
Event(s) for the `outbound_payments` resource type.
Content-Type: application/json
PayerAuthorisationEvent
Event(s) for the `payer_authorisations` resource type.
Content-Type: application/json
PaymentEvent
Event(s) for the `payments` resource type.
Content-Type: application/json
PaymentAccountTransactionEvent
Event(s) for the `payment_account_transaction` resource type.
Content-Type: application/json
PayoutEvent
Event(s) for the `payouts` resource type.
Content-Type: application/json
RefundEvent
Event(s) for the `refunds` resource type.
Content-Type: application/json
SchemeIdentifierEvent
Event(s) for the `scheme_identifiers` resource type.
Content-Type: application/json
SubscriptionEvent
Event(s) for the `subscriptions` resource type.
Content-Type: application/json
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.