Payloads
Field-level schema for Flo webhook payloads.
Payloads
Each Flo webhook message contains one normalized Flo event payload.
For concrete examples of delivered events, see Events.
Common Fields
Event Envelope
eventId: The Flo webhook delivery identifier for this endpoint delivery. It is not the upstream gateway event id, and automatic retries for the same delivery reuse the sameeventId.eventVersion: The webhook schema version.objectType: The top-level Flo resource family for the event.eventType: The normalized Flo event type.user: The canonical user object for the event.subscription: Present on subscription events. May also be present on invoice events as related enrichment.item: Present on item events. May also be present on invoice events as related enrichment.invoice: Present on invoice events.
Compatibility Fields
New integrations should build against user, eventType, objectType, and the explicit resource root (subscription, item, or invoice).
On invoice events, root-level subscription and item are enrichment fields. Flo includes them when the invoice points at a linked local transaction that resolves to a checkout subscription and/or checkout item.
User Object
Subscription Payload
uuid: Flo's checkout subscription UUID when the event is linked to a checkout session.id: The checkout subscription's provider plan id.name/description: The checkout subscription's provider-backed display fields.
Item Payload
uuid: Flo's checkout item UUID when the event is linked to a checkout session.id: The checkout item's provider item id.name/description: The checkout item's provider-backed display fields.
Invoice Payload
Invoice Event Enrichment
- On invoice events, Flo may include root-level
subscriptionand/oritemalongsideinvoice. - These related objects are resolved from the linked local transaction.
- An invoice event can include either, both, or neither of these related objects.
Invoice-related Subscription Payload
Invoice-related Item Payload
Invoice Details
invoiceDetails is optional on subscription, item, and invoice events. When present, it includes invoice and payment context associated with the Flo event.
Most integrations should build against eventType, objectType, and the explicit resource root (subscription, item, or invoice). invoiceDetails.gatewayEventType is additional trace context and should not be the primary switch for business logic.