AsyncAPI channel · Simplifi/Simplifipay · SimpliFi Webhooks

{clientConfiguredEndpoint}

Open source AsyncAPI → All Simplifi/Simplifipay channels Simplifi/Simplifipay provider profile
Provider: Simplifi/Simplifipay AsyncAPI: v3.0.0 Spec: SimpliFi Webhooks Operations: 1 Messages: 25

Channel address

{clientConfiguredEndpoint}

Parameters

Operations

receive
receiveWebhook
Receive a SimpliFi webhook event.

Messages

CARD_ACTIVATION
Delivered when a Card Activation operation completes (SUCCESS or FAILURE).
Content-Type:
CARD_ISSUANCE
Delivered when a Card Issuance operation completes (SUCCESS or FAILURE).
Content-Type:
CARD_PIN_SETUP
Delivered when a Card Pin Setup operation completes (SUCCESS or FAILURE).
Content-Type:
CARD_RENEWED
Delivered when a Card Renewed operation completes (SUCCESS or FAILURE).
Content-Type:
CARD_STATUS_CHANGE
Delivered when a Card Status Change operation completes (SUCCESS or FAILURE).
Content-Type:
CARD_TYPE_CHANGE
Delivered when a Card Type Change operation completes (SUCCESS or FAILURE).
Content-Type:
CARD_RULE_GROUP_CREATION
Delivered when a Card Rule Group Creation operation completes (SUCCESS or FAILURE).
Content-Type:
CARD_RULE_GROUP_DELETION
Delivered when a Card Rule Group Deletion operation completes (SUCCESS or FAILURE).
Content-Type:
CARD_LOAD
Delivered when a Card Load operation completes (SUCCESS or FAILURE).
Content-Type:
CARD_UNLOAD
Delivered when a Card Unload operation completes (SUCCESS or FAILURE).
Content-Type:
CARD_TO_CARD_TRANSFER
Delivered when a Card To Card Transfer operation completes (SUCCESS or FAILURE).
Content-Type:
CARD_HOLDER_CREATION
Delivered when a Card Holder Creation operation completes (SUCCESS or FAILURE).
Content-Type:
CARD_HOLDER_UPDATION
Delivered when a Card Holder Updation operation completes (SUCCESS or FAILURE).
Content-Type:
CARD_HOLDER_DELETION
Delivered when a Card Holder Deletion operation completes (SUCCESS or FAILURE).
Content-Type:
CARD_PROGRAM_CREATION
Delivered when a Card Program Creation operation completes (SUCCESS or FAILURE).
Content-Type:
WALLET_RULE_GROUP_CREATION
Delivered when a Wallet Rule Group Creation operation completes (SUCCESS or FAILURE).
Content-Type:
WALLET_RULE_GROUP_DELETION
Delivered when a Wallet Rule Group Deletion operation completes (SUCCESS or FAILURE).
Content-Type:
FUNDS_TRANSFER
Delivered when a Funds Transfer operation completes (SUCCESS or FAILURE).
Content-Type:
RAISE_FUNDING_SOURCE
Delivered when a Raise Funding Source operation completes (SUCCESS or FAILURE).
Content-Type:
RULE_GROUP_CREATION
Delivered when a Rule Group Creation operation completes (SUCCESS or FAILURE).
Content-Type:
RULE_GROUP_UPDATION
Delivered when a Rule Group Updation operation completes (SUCCESS or FAILURE).
Content-Type:
RULE_GROUP_DELETION
Delivered when a Rule Group Deletion operation completes (SUCCESS or FAILURE).
Content-Type:
TRANSACTION
Delivered when a Transaction operation completes (SUCCESS or FAILURE).
Content-Type:
TRANSACTION_ENRICHMENT
Delivered when a Transaction Enrichment operation completes (SUCCESS or FAILURE).
Content-Type:
FEES_APPLY
Delivered when a Fees Apply operation completes (SUCCESS or FAILURE).
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.