API Integration
API Integration
Drive Churn Buster from your own backend: failed/succeeded payments, cancellations, the customer endpoint, upcoming-renewal hints, and outbound webhooks.
Getting Started with the Churn Buster API
The auth model, the four endpoints you'll use most, and how to wire them up from an in-house subscription stack.
Successful Payments API Endpoint
Notify Churn Buster of (recurring) successful payments so that recovery campaigns can be ended (if active) and analytics can be tracked.
Failed Payments API Endpoint
Notify Churn Buster of failed, recurring payments to trigger recovery campaigns.
Cancellations API Endpoint
Notify Churn Buster of subscription cancellations so that recovery campaigns can be ended (if active) and analytics can be tracked.
Default Payment Method API Endpoint (always optional)
Notify Churn Buster when a customer's default payment method is updated so that analytics can be tracked.
Customer Endpoint
Sync customer profile data into Churn Buster so emails personalize correctly and segmentation has real signal.
Upcoming Annual Renewals API Endpoint
[Optional] Send a branded email to customers notifying them of their upcoming annual renewal. This feature is only available to Enterprise accounts, and requires setup assistance from the Churn Buster team.
Webhook Data Reference
What Churn Buster sends in outbound webhooks: payload shape, event types, and how to consume them.