Use Cases
Developer API v1

What this API is for

Connect your own systems to the Funnels.cm checkout and marketing infrastructure. Receive real-time events via webhooks, push tagged contacts via REST.

01

Grant access after a specific checkout

Pick the checkout in Settings → API webhooks, then map data.product.id to a plan on your server.

OutboundListen: checkout.purchased · checkout.rebilled · checkout.refunded
InboundOptional: GET/POST /checkout/activations/:token for SaaS Signup
View docs →
02

Push leads into your marketing stack

Send tagged contacts from your CRM, ads, or backend into Funnels.cm automations.

Outbound-
InboundPOST /api/v1/contacts with email + tagIds or tagNames
View docs →
03

React to forms & calendar bookings

Sync submissions and bookings to your database, Slack, or internal tools in real time.

OutboundListen: form.submitted · scheduling.booked
Inbound-
View docs →
04

Mirror checkout events in your app

Map product IDs and pricing tiers to plans, track MRR, and trigger onboarding on payment.

OutboundListen: checkout.purchased with data.product.id + data.pricing.tierIndex
Inbound-
View docs →
05

Upgrade or downgrade SaaS plans

No change-plan API — map tiers on purchase, then cancel the old subscription and rebuy (or buy then cancel).

OutboundListen: checkout.purchased · checkout.subscription_cancel_scheduled · checkout.subscription_cancelled
Inbound-
View docs →
→
Two directions

Outbound - Funnels.cm POSTs events to your URL when forms submit, calendars book, or checkout charges.
Inbound - Your backend POSTs contacts + tags into Funnels.cm to trigger automations.

→
Account-specific setup lives in the app

Checkout ids, form scope, calendar scope, tag names, and your Secret API key are configured in Settings → Integration → API in Funnels.cm. The docs at api.funnels.cm describe the HTTP contract; the app shows your account's exact ids and webhook scope.

Base URL https://api.funnels.cm Auth Authorization: Bearer <secret-api-key>