Flint sends signed webhook events when payments, orders, subscriptions, refunds, and invoices change, following the Standard Webhooks specification. Use them as the durable trigger for fulfillment, entitlement updates, and downstream synchronization rather than polling.
Register an endpoint with an HTTPS URL and an optional enabled_events list (omit the list to receive everything). Flint delivers events as signed JSON POST requests with Standard Webhooks headers (webhook-id, webhook-timestamp, and webhook-signature), plus legacy X-Flint-* compatibility headers. Failed deliveries are retried on the documented backoff schedule. The signing secret is returned only at creation and rotation, and rotation keeps the previous secret valid for a 24-hour overlap so you can deploy without downtime. Beyond endpoint management, this surface lets you list delivered events, inspect per-attempt delivery history, send synthetic test events, and manually resend an event.
See the Webhooks guide for registration and signature verification examples, and the event catalog for event types and documented payload shapes.
Include an optional reason_message when resending a webhook delivery to record your note. The delivery action and its attempt echo the note as reason_message.
