The offer record connects the stack
Use Offers to define the product, price, checkout mode, invoice, and automation context before Custom API and Kit (ConvertKit) receive events.
Integration pair
Custom API + Kit (ConvertKit)
Use Custom API and Kit (ConvertKit) together with Plandalf as the layer that ties checkout, payments, invoices, integrations, and lifecycle automation together.
Common setup
Most teams use Custom API as their sdk layer and Kit (ConvertKit) as their email layer, with Plandalf in the middle handling the checkout, Offers, invoices, integrations, and the events that fire after a purchase.
See Custom API and Kit (ConvertKit) docs for connection details.
Product surfaces behind this integration
This legacy integration URL now points builders toward the same product reality as the canonical app-pair guide: Offers, payment options, invoices, integrations, Automations, API docs, and webhooks.
Purchase automation carries the details
Automations and webhooks let Custom API and Kit (ConvertKit) receive buyer, product, payment, invoice, coupon, and deadline context.
Integration settings remain visible
Confirm Stripe, PayPal, TaxJar, Avalara, and test-mode routing before sending the Custom API and Kit (ConvertKit) path live.
Use the richer guide from here
Keep moving from this page into canonical integration docs, platform pages, stack guides, and sequence recipes so every Custom API or Kit (ConvertKit) mention has a useful next step.
Open canonical app-pair guide Use the richer Custom API and Kit (ConvertKit) implementation guide. Custom API platform page Roles, capabilities, and setup notes for Custom API. Kit (ConvertKit) platform page Roles, capabilities, and setup notes for Kit (ConvertKit). API-first stack SDK checkout, API keys, webhooks, payment processors, and invoices.