- Subscription endpoint:
POST /v1/notifications/subscriptions - Setup: Circle APIs notifications quickstart
| Envelope field | Type | Description |
|---|---|---|
clientId | string | Your Circle client identifier. |
notificationType | string | Event type identifier. See Event types. |
version | number | Schema version. Always 1. |
<resourceKey> | object | Event-specific data. The key name varies by event type. |
Event types
notificationType | Resource key | Trigger |
|---|---|---|
paymentIntents | paymentIntent | Intent created, deposit address assigned, or (transient intents) intent completed. |
payments | payment | A payin settles, or a refund changes status. Discriminated by type. |
addressBookRecipients | addressBookRecipient | Recipient status changes, such as pending to active. |
payouts | payout | Payout status changes, such as pending, complete, or failed. |
Payment intent events
ThepaymentIntents notification fires when you create an intent, when Circle
assigns the deposit address, and—for transient intents—when the intent reaches
complete. Continuous intents stay at active and never advance to complete;
reconcile their transfers through the payments event instead.
Status values observed in timeline[].status: created, pending, active,
complete.
Example paymentIntents payload
Payment events
Thepayments notification fires whenever an inbound transfer settles or a
refund changes status. Payments and refunds share this channel and are
discriminated by the type field (payment or refund). The payload links
back to its intent through paymentIntentId.
Status values: pending, paid.
Example payments payload
Address book recipient events
TheaddressBookRecipients notification fires when a recipient’s status
changes, such as when review completes and the recipient becomes active. Wait
for active before you send a payout to the recipient.
Status values: pending, inactive, active, denied.
Example addressBookRecipients payload
Payout events
Thepayouts notification fires when a payout status changes. The payload
includes the resolved fees and onchain networkFees.
Status values: pending, complete, failed.
Example payouts payload