AsyncAPI channel · Coinbase · Coinbase Commerce Webhooks

/webhook

Webhook endpoint that receives Commerce event notifications. All events are delivered as HTTPS POST requests with a JSON payload and X-CC-Webhook-Signature header for verification.

Provider: Coinbase AsyncAPI: v2.6.0 Spec: Coinbase Commerce Webhooks Operations: 1 Messages: 6

Channel address

/webhook

Operations

publish
receiveCommerceWebhook
Receive Commerce webhook events

Messages

charge:created
Fired when a new charge is created
Content-Type: application/json
charge:confirmed
Fired when a charge receives sufficient blockchain confirmations
Content-Type: application/json
charge:failed
Fired when a charge expires without receiving payment
Content-Type: application/json
charge:delayed
Fired when a charge payment is detected but awaiting confirmations
Content-Type: application/json
charge:pending
Fired when a charge payment is pending
Content-Type: application/json
charge:resolved
Fired when an unresolved charge is manually resolved
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.