AsyncAPI channel · FastSpring · FastSpring Webhooks

webhook

Single delivery channel for all FastSpring webhook events. The request body is an envelope containing an `events` array; each entry carries a `type` discriminator and an event-specific `data` payload. Subscribe semantics here describe the seller endpoint receiving events from FastSpring.

Provider: FastSpring AsyncAPI: v2.6.0 Spec: FastSpring Webhooks Operations: 1 Messages: 24

Channel address

webhook

Operations

receiveFastSpringWebhook
Receive FastSpring webhook events

Messages

account.created
A new customer account was created.
Content-Type:
account.updated
An existing customer account was updated.
Content-Type:
order.approval.pending
An order is awaiting buyer/approver action (e.g. invoice-based purchases).
Content-Type:
order.canceled
An order was canceled before completion.
Content-Type:
order.completed
An order completed successfully and payment was captured.
Content-Type:
order.failed
An order attempt failed (e.g. declined payment).
Content-Type:
order.payment.pending
An order is awaiting asynchronous payment confirmation.
Content-Type:
order.chargeback
A chargeback or dispute was filed against an order.
Content-Type:
mailingListEntry
A buyer subscribed via abandoned-cart or remarketing capture.
Content-Type:
quote.created
A new B2B quote was created.
Content-Type:
quote.updated
An existing B2B quote was updated.
Content-Type:
return.created
A refund or return was created against a prior order.
Content-Type:
payoutEntry.created
A new order or return entry was created for payout processing.
Content-Type:
fulfillment.failed
A fulfillment action (license/file/script) failed.
Content-Type:
subscription.activated
A new subscription was activated (including trial start).
Content-Type:
subscription.canceled
A subscription was canceled (effective at end of current period).
Content-Type:
subscription.charge.completed
A recurring subscription charge succeeded.
Content-Type:
subscription.charge.failed
A recurring subscription charge failed (dunning may begin).
Content-Type:
subscription.deactivated
A subscription was deactivated (entitlement should end).
Content-Type:
subscription.payment.overdue
A subscription is past due on a recurring charge.
Content-Type:
subscription.payment.reminder
A scheduled rebill is approaching for a subscription.
Content-Type:
subscription.trial.reminder
A subscription trial is approaching its end.
Content-Type:
subscription.uncanceled
A previously canceled subscription was reinstated.
Content-Type:
subscription.updated
A subscription's details (plan, add-ons, schedule) were updated.
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.

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.