AsyncAPI channel · Ramp · Ramp Developer API Webhooks

ramp/webhook

Single inbound channel that receives every Ramp webhook event. Consumers route on the envelope `type` field. The complete list of event types is enumerated in the `RampEventType` schema.

Provider: Ramp AsyncAPI: v2.6.0 Spec: Ramp Developer API Webhooks Operations: 1 Messages: 36

Channel address

ramp/webhook

Operations

receiveRampWebhook
Receive a Ramp webhook event.

Messages

ApplicationsStatusUpdated
Fired when a Ramp application status changes (e.g. IN_REVIEW, APPROVED, REJECTED).
Content-Type:
BillsApproved
Fired when a bill is approved.
Content-Type:
BillsArchived
Fired when a bill is archived.
Content-Type:
BillsCreated
Fired when a new bill is created.
Content-Type:
BillsPaid
Fired when a bill payment completes.
Content-Type:
BillsReadyToSync
Fired when a bill is ready to sync to accounting.
Content-Type:
BillsRejected
Fired when a bill is rejected.
Content-Type:
EntitiesCreated
Fired when a business entity is created.
Content-Type:
ItemReceiptsCreated
Fired when an item receipt is created.
Content-Type:
PaymentsUpdated
Fired when a bill payment state updates.
Content-Type:
PurchaseOrdersArchived
Fired when a purchase order is archived.
Content-Type:
PurchaseOrdersCreated
Fired when a purchase order is created.
Content-Type:
PurchaseOrdersUpdated
Fired when a purchase order is updated.
Content-Type:
ReimbursementsBatchPaymentReimbursed
Fired when a batch reimbursement payment is disbursed.
Content-Type:
ReimbursementsReadyForReview
Fired when a reimbursement is ready for review.
Content-Type:
ReimbursementsReadyToSync
Fired when a reimbursement is ready to sync to accounting.
Content-Type:
ReimbursementsSyncRequested
Fired when a reimbursement sync is requested.
Content-Type:
SpendRequestsCommentCreated
Fired when a comment is added to a spend request.
Content-Type:
TransactionsAuthorized
Fired when a corporate-card transaction is authorized.
Content-Type:
TransactionsCleared
Fired when a corporate-card transaction settles/clears.
Content-Type:
TransactionsDeclined
Fired when a corporate-card transaction is declined.
Content-Type:
TransactionsReadyForReview
Fired when a transaction is ready for review.
Content-Type:
TransactionsReadyToSync
Fired when a transaction is ready to sync to accounting.
Content-Type:
TransactionsSyncRequested
Fired when a transaction sync is requested.
Content-Type:
TransactionsSynced
Fired when a transaction has been synced to accounting.
Content-Type:
UnifiedRequestsCreated
Fired when a unified request is created.
Content-Type:
UnifiedRequestsExternalApprovalRequest
Fired when a unified request requires external approval.
Content-Type:
UnifiedRequestsExternalApprovalRequestReset
Fired when an external approval request on a unified request is reset.
Content-Type:
UnifiedRequestsModified
Fired when a unified request is modified.
Content-Type:
UnifiedRequestsNodeAdvanced
Fired when a unified request advances to the next approval node.
Content-Type:
UnifiedRequestsOverrideApproved
Fired when a unified request is approved via override.
Content-Type:
UnifiedRequestsUpdated
Fired when a unified request is updated.
Content-Type:
UsersInviteAccepted
Fired when an invited user accepts their Ramp invitation.
Content-Type:
VendorsActivated
Fired when a vendor is activated.
Content-Type:
VendorsUpdated
Fired when a vendor record is updated.
Content-Type:
TestsTestEvent
Test event delivered when a subscription's test action is invoked.
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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.