Outbound webhooks are available for provisioned customer integrations. Ask your FloKit operator to enable an endpoint for the required Company, App, and environment.
subscription_started, displayed in Admin as Initial successful subscription payment.
For Stripe, the source is a verified invoice.paid invoice that claims the subscription’s first-paid marker. An opening invoice worth zero, a later renewal, a checkout completion page, and a browser callback do not create this event. If the invoice arrives before its subscription, FloKit reconciles the two records and retains the invoice’s source Event reference.
The payload contains the FloKit Payment and Subscription IDs, separate provider references, the purchased Package, customer identity, and the final answered questionnaire from the published Flow. A Flow with no questionnaire omits the questionnaire property. Optional values are omitted when unavailable.
Delivery is at least once. Your receiver must verify the signature over the raw bytes, durably store or queue the event under a unique event_id, and return 200 or 204 after that transaction commits. A timeout can lead to another request even when your first request committed successfully.
Each endpoint is scoped to one Company, App, and environment. New endpoints receive future events; creating an endpoint does not backfill historical purchases. All endpoints belonging to a Company share that Company’s signing secret.
Start with Setup, then implement Signature verification. See the payload field reference and delivery and troubleshooting guide.
These are requests from FloKit to your server. For payment-provider requests into FloKit, see Stripe Direct setup or Paddle notifications.