ThriveCart Webhook

thrivecart-webhook

ThriveCart POSTs checkout notifications when orders complete, rebill, refund, cancel, or when carts abandon. Each POST is one stored report. ThriveCart uses two delivery surfaces with different event vocabularies — inspect the stored payload to see which landed:

• Account webhooks — dotted keys such as order.success, order.subscription_payment, order.refund. Body is often form-encoded with nested bracket keys (customer[email], order[total]).
• Event subscriptions — underscore keys such as order_payment_product, order_rebill, order_rebill_cancelled. Body is JSON.

ThriveCart does not publish complete payload schemas; fields vary by funnel, processor, bumps/upsells, and event type. Read the latest stored delivery rather than assuming a fixed shape.

First moves

1. Latest report — default for “what order or subscription event happened last”.
2. Check event — classify the delivery before quoting amounts or customer details.
3. Recent reports — list when comparing rebills, refunds, or duplicate deliveries.
4. One report by id — after listing, when the user names a specific capture.

Payload envelope (common across many events)

Fields often present at the top level:

• event — what happened (dotted or underscore key depending on surface).
• webhook_id — delivery id; stable across retries of the same POST (use for deduping).
• event_id — legacy transaction/event record id; may be absent on some event types.
• mode / mode_int — test vs live (mode_int 1 = test, 2 = live).
• thrivecart_account — account subdomain identifier.
• order_id, base_product, invoice_id — order and product context.
• currency — three-letter code (USD, GBP, …).
• customer_id, customer — buyer id and nested contact block (email, name, firstname, lastname, address with country/state/city/zip).
• order — totals and payment context: total, total_str, tax, tax_type, processor (stripe/paypal), payment_method, charges[], future_charges[], date, date_unix.

Order and subscription events to expect

Account webhooks (event dotted):

• order.success — initial purchase (one-time or subscription start); includes purchases, purchase_map, purchase_map_flat, fulfillment, transactions, subscriptions.
• order.subscription_payment — recurring charge; includes recurring_payment_idx, subscription{type,id,name,processor,amount,amount_str}.
• order.subscription_cancelled, order.subscription_paused, order.subscription_resumed — lifecycle changes with a subscription block.
• order.refund — includes refund{amount,amount_str,type,id,name,processor}.
• order.rebill_failed, cart.abandoned — failed payment and abandoned-cart signals.

Event subscriptions (event underscore):

• order_payment_product, order_payment_bump, order_payment_upsell, order_payment_downsell — line-item purchase events.
• order_rebill, order_rebill_completed, order_rebill_failed, order_rebill_cancelled — subscription or split-pay billing cycle.
• order_refund_product, order_refund_bump, order_refund_upsell, order_refund_downsell — refunds by line type.
• subscription_paused, subscription_resumed, cart_abandoned — lifecycle and recovery signals.

Affiliate commission events (affiliate.commission_* or affiliate_commission_*) may also appear if configured upstream.

Money and line items

• Amount integers are in hundredths of the currency unit (1499 = 14.99); many fields also include *_str decimal strings (total_str, amount_str).
• order.charges[] — line charges with type (single vs recurring), name, reference, amount, frequency, payment_plan_id, item_type, item_identifier.
• purchases / purchase_map — human-readable names and ids like product-12, bump-12, upsell-2.

Response shape (stored reports)

• export.json — parsed object when the inbound body was JSON.
• export.text — raw body when form-encoded, large, or non-object.
• source.captured_at — when the delivery landed here (compare to order.date / order_timestamp in the payload for checkout time).

Operational order

1. Start with the latest report — do not guess a report id.
2. Read event first, then customer email and order totals.
3. List recent reports only for history, rebill sequences, or duplicate suspicion.
4. Read ## This connection in the skill supplement for funnel-specific field notes.

Gotchas

• Read-only — cannot refund, cancel subscriptions, or replay events upstream.
• Two event vocabularies — order.success and order_payment_product describe related facts with different keys; never assume one naming scheme.
• Incomplete schemas — passthrough checkout fields and processor-specific keys may appear; inspect actual stored JSON.
• Test vs live — always check mode_int before treating revenue as production.
• Retries — same webhook_id means duplicate delivery, not a new order.
• Form-encoded bodies — nested objects may flatten to bracket keys in export.text; parse carefully.