AsyncAPI channel · Finix
· Finix Webhook Events
low_code
Channel address
low_code
Operations
subscribe
subscribe low_code
Messages
checkout_form.created
Checkout interface deployed.
Content-Type:
checkout_form.updated
Checkout form configuration modified.
Content-Type:
payment_link.created
Payment link generated.
Content-Type:
payment_link.updated
Payment link settings changed.
Content-Type:
subscription.created
Recurring billing plan activated.
Content-Type:
subscription.updated
Subscription state or details changed.
Content-Type:
payout_profile.created
Seller payout configuration established.
Content-Type:
application.created
New application created (Core customers only).
Content-Type:
application.updated
Application modified.
Content-Type:
application_profile.created
Application profile established.
Content-Type:
application_profile.updated
Application profile changed.
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.