AsyncAPI channel · Celery
· Celery Worker Event Stream
celeryev
Lifecycle events for individual task executions.
Channel address
celeryev
Operations
receive
receiveTaskEvents
Consume task lifecycle events (celery events, Flower, or a custom EventReceiver).
Messages
task-sent
Sent when a task message is published and the task_send_sent_event setting is enabled.
Content-Type:
task-received
Sent when the worker receives a task.
Content-Type:
task-started
Sent just before the worker executes the task.
Content-Type:
task-succeeded
Sent if the task executed successfully.
Content-Type:
task-failed
Sent if the execution of the task failed.
Content-Type:
task-rejected
The task was rejected by the worker, possibly to be re-queued or moved to a dead letter queue.
Content-Type:
task-revoked
Sent if the task has been revoked. The documentation notes this is likely to be sent by more than one worker.
Content-Type:
task-retried
Sent if the task failed, but will be retried in the future.
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.