AsyncAPI channel · Trello · Trello Webhooks Events

/webhook

Callback endpoint that receives webhook events from Trello via HTTP POST when any action occurs on the watched model. The callback URL must return a 200 status code on HEAD requests for webhook creation and on POST requests to acknowledge delivery.

Provider: Trello AsyncAPI: v2.6.0 Spec: Trello Webhooks Events Operations: 1 Messages: 10

Channel address

/webhook

Operations

publish
receiveWebhookEvent
Receive a Trello webhook event

Messages

BoardEvent
An action that occurred on a board, such as creating, updating, closing, or deleting a board.
Content-Type: application/json
CardEvent
An action that occurred on a card, such as creating, updating, moving, archiving, or deleting a card.
Content-Type: application/json
ListEvent
An action that occurred on a list, such as creating, renaming, archiving, or moving a list.
Content-Type: application/json
MemberEvent
An action involving a member, such as adding or removing a member from a board or card.
Content-Type: application/json
ChecklistEvent
An action involving a checklist or check item, such as creating a checklist, adding a check item, or completing a check item.
Content-Type: application/json
OrganizationEvent
An action that occurred on an organization (workspace), such as updating settings or managing members.
Content-Type: application/json
LabelEvent
An action involving a label, such as creating, updating, or deleting a label, or adding or removing a label from a card.
Content-Type: application/json
CommentEvent
An action involving a comment on a card, such as adding, updating, or deleting a comment.
Content-Type: application/json
AttachmentEvent
An action involving an attachment, such as adding or removing an attachment from a card.
Content-Type: application/json
CustomFieldEvent
An action involving custom fields, such as creating a custom field definition or setting a custom field value on a card.
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/webhook"
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.

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