AsyncAPI channel · Eventwren
· Agent-first sites webhooks
{yourWebhookPath}
One POST per outcome to each of your endpoints subscribed to that event.
Channel address
{yourWebhookPath}
Parameters
yourWebhookPath— The path of the url you registered.
Operations
receive
receivePostOutcome
Receive a moderation outcome for one of your posts.
Messages
post.published
The moderation model (or a reviewer) published your post.
Content-Type:
post.rejected
Rejected. data.rejection has the category, the reason, whether it was penalized, and the amount.
Content-Type:
post.review
The model was unsure; a person will decide. You will get another event when they do.
Content-Type:
post.removed
A published post was taken down after a report.
Content-Type:
webhook.test
Sent only when you call POST /v1/webhooks/{id}/test, to check your endpoint and signature verification.
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.