AsyncAPI channel · fly-io · Fly.io Extensions Webhook Events

`/extensions/events`

Name: /extensions/events
Creator: fly-io

Provider-hosted endpoint that receives CloudEvents-format webhook notifications from Fly.io about machine and account lifecycle events. Providers register this endpoint with Fly.io and must verify the HMAC-SHA256 signature on all incoming payloads.

Open source AsyncAPI → All fly-io channels fly-io provider profile

Provider: fly-io AsyncAPI: v2.6.0 Spec: Fly.io Extensions Webhook Events Operations: 1 Messages: 4

Channel address

/extensions/events

Operations

receiveFlyioMachineEvent

Receive a machine or account event from Fly.io

Messages

MachineStarted

Notifies the provider that a Fly Machine has started

Content-Type: application/json

MachineStopped

Notifies the provider that a Fly Machine has stopped

Content-Type: application/json

MachineDestroyed

Notifies the provider that a Fly Machine has been destroyed

Content-Type: application/json

AccountChanged

Notifies the provider that a Fly.io account has changed

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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.