AsyncAPI channel · GoCardless · GoCardless Webhooks

`/`

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.

Open source AsyncAPI → All GoCardless channels GoCardless provider profile

Provider: GoCardless AsyncAPI: v2.6.0 Spec: GoCardless Webhooks Operations: 1 Messages: 14

Channel address

/

Operations

publish

receiveWebhook

Receive a webhook delivery from GoCardless

Messages

BillingRequestEvent

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.

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.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for event channels

4 MCP tools reach this

find_channelsBrowse and filter every channel in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This channel

curl "https://apis.io/api/v1/channels/untitled"

All event channels

curl "https://apis.io/api/v1/channels?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.