Outbound webhook data reference

Outbound Webhooks send information to third-party applications when specific actions occur in Kajabi. This article covers all the fields sent for Purchase Created, Payment Succeeded, Cart Purchase, and Form Submission webhooks.

​

Outbound webhooks

What are outbound webhooks? An Outbound Webhook sends information to a third-party application when an action occurs in Kajabi. An Outbound Webhook can be used when you would like to send information (including name, email, and transaction information) to a third-party application after a purchase has been made in Kajabi. Learn how to use webhooks on Kajabi.

​

Purchase Created webhooks

The following fields are sent to your third-party applications when a customer purchases a one-time offer, their first payment for a subscription, or a payment plan offer. Please note that this does not include purchases made through Kajabi Cart. For cart orders, please refer to the Cart Purchase Webhooks section below.

​

ID

• id - Unique Identifier for the transaction.

​

Offer

Offer information associated with the payment at the time of the transaction.

• id - Unique Identifier for the Kajabi offer
• title - The title of the Kajabi Offer that was purchased

​

Member

Contact information associated with the payment at the time of transaction.

• id - Unique Identifier for the customer’s contact record who made a payment transaction
• email - The contact record’s email address at the time of the payment transaction
• name - The contact record’s full name at the time of the payment transaction
• first_name - The contact record’s first name at the time of the payment transaction
• last_name - The contact record’s last name at the time of the payment transaction

​

Extra contact information

Additional contact details collected at the time of the transaction, if enabled in the Offer settings.

• address_line_1 - Customer’s address line 1 (e.g., street, PO Box, or company name), if collected at the time of checkout
• address_line_2 - Customer’s address line 2 (e.g., apartment, suite, unit, or building), if collected at the time of checkout
• address_city - Customer’s city, district, suburb, town, or village, if collected at the time of checkout
• address_country - Customer’s two-letter country code, if collected at the time of checkout
• address_country_name - Customer’s full name of country, if collected at the time of checkout
• address_state - Customer’s state, county, province, or region, if collected at the time of checkout
• address_zip - Customer’s ZIP or postal code, if collected at the time of checkout
• phone_number - Customer’s phone number, if collected at the time of checkout
• business_number - Customer’s business/tax number, if collected at the time of checkout
• custom_fieldname - Custom form fields and submitted values at the time of checkout (e.g., custom_1, custom_2, etc.)

​

Payment Succeeded webhooks

​

Attributes

• id - Unique identifier for the event.
• Event - String representing the event type. For example, “payment.succeeded” occurs whenever a payment is successful.

​

Offer (won’t show for orders with multiple Offers)

Offer information associated with the payment at the time of the transaction.

• id - Unique Identifier for the Kajabi offer.
• title - The title of the Kajabi Offer that was purchased.
• internal_title - The internal title of the Kajabi offer that was purchased.
• type - Kajabi Offer type. Can be one-time, subscription, payment plan, or free.

​

Member

Contact information associated with the payment at the time of transaction.

• id - Unique Identifier for the customer’s contact record who made a payment transaction.
• email - The contact record’s email address at the time of the payment transaction.
• name - The contact record’s full name at the time of the payment transaction.
• first_name - The contact record’s first name at the time of the payment transaction.
• last_name - The contact record’s last name at the time of the payment transaction.

​

Payment transaction

Payment information associated at the time of transaction.

• id - Unique identifier for the transaction.
• created_at - Date and time at which the transaction was created.
• payment_processor - Processor used for the transaction (e.g., “Kajabi Payments”, “Stripe”).
• payment_method - Payment method used for the transaction.
• currency - Three-letter ISO currency code.
• coupon_code - Coupon code used, if applicable.
• subtotal - Order subtotal, in currency’s smallest unit, before discounts and taxes.
• discount_amount - Total discount amount for the order, in currency’s smallest unit.
• sales_tax - Total sales tax for the order, in currency’s smallest unit.
• amount_paid - Total amount paid after discounts and taxes, in currency’s smallest unit.

​

Cart Purchase webhooks

​

Order

Order information associated with the cart purchase.

• id - Unique identifier for the order.
• source - The origin of the order (e.g., “cart”).
• order_number - The order number assigned to this cart order.
• order_items - An array of items included in the cart order. Each order item contains the following fields:
  • type - The type of item (e.g., “Offer”).
  • id - Unique identifier for the item (e.g., the Offer ID).
  • title - The title of the item at the time of purchase.
  • internal_title - The internal title of the item, if set.
  • quantity - The quantity of this item purchased.
  • unit_cost - The unit price of the item, in currency’s smallest unit (e.g., cents).
  • unit_cost_decimal - The unit price of the item. Formatted with decimal places if applicable.
  • subtotal - The line item subtotal (unit cost × quantity), in currency’s smallest unit, before discounts and taxes.
  • subtotal_decimal - The line item subtotal. Formatted with decimal places if applicable.
  • discount_amount - The discount applied to this line item, in currency’s smallest unit.
  • discount_amount_decimal - The discount applied to this line item. Formatted with decimal places if applicable.
  • sales_tax - Sales tax for this line item, in currency’s smallest unit.
  • sales_tax_decimal - Sales tax for this line item. Formatted with decimal places if applicable.
  • total_amount - The total for this line item after discounts and taxes, in currency’s smallest unit.
  • total_amount_decimal - The total for this line item. Formatted with decimal places if applicable.

​

Payment transaction

Transaction details for the cart purchase.

• id - Unique identifier for the transaction.
• created_at - Date and time at which the transaction was created.
• payment_processor - Processor used for the transaction (e.g., “Kajabi Payments”, “Stripe”).
• payment_method - Payment method used for the transaction. For Kajabi Payments, this is more granular (e.g., visa, mastercard, apple_pay, etc.).
• payment_method_country - Two-letter country code of the payment method, if available.
• currency - Three-letter ISO currency code.
• coupon_code - Coupon code used, if applicable.
• subtotal - Order subtotal, in currency’s smallest unit, before discounts and taxes.
• subtotal_decimal - Order subtotal. Formatted with decimal places if applicable.
• discount_amount - Total discount amount for the order, in currency’s smallest unit.
• discount_amount_decimal - Total discount amount. Formatted with decimal places if applicable.
• sales_tax - Total sales tax for the order, in currency’s smallest unit.
• sales_tax_decimal - Total sales tax. Formatted with decimal places if applicable.
• amount_paid - Total amount paid after discounts and taxes, in currency’s smallest unit.
• amount_paid_decimal - Total amount paid. Formatted with decimal places if applicable.
• receipt_number - General receipt/invoice ID for the transaction.

​

Kajabi Payments fields (if applicable)

These fields are only included when Kajabi Payments is the payment processor:

• fee_amount - Processing fees, in currency’s smallest unit (cents).
• fee_amount_decimal - Processing fees. Formatted with decimal places if applicable.
• net_amount - Net amount after fees, in currency’s smallest unit (cents).
• net_amount_decimal - Net amount after fees. Formatted with decimal places if applicable.

​

Settlement fields (if applicable)

These fields are only included when a cross-currency settlement exists (Kajabi Payments):

• settlement_currency - The currency code of the settlement/transfer.
• settlement_amount - Settlement amount in the settlement currency’s smallest unit.
• settlement_amount_decimal - Settlement amount. Formatted with decimal places if applicable.
• settlement_net_amount - Net settlement amount after fees, in the settlement currency’s smallest unit.
• settlement_net_amount_decimal - Net settlement amount. Formatted with decimal places if applicable.

​

Invoice fields (if applicable)

• invoice_number - Only included for invoice-based orders.

​

Member

Contact information associated with the payment at the time of the transaction.

• id - Unique identifier for the customer’s contact record.
• email - The contact record’s email address at the time of the transaction.
• name - The contact record’s full name at the time of the transaction.
• first_name - The contact record’s first name at the time of the transaction.
• last_name - The contact record’s last name at the time of the transaction.

​

Extra contact information

Additional contact details collected at the time of the transaction, if enabled. Only fields with values are included.

• address_line_1 - Customer’s address line 1 (e.g., street, PO Box, or company name), if collected at checkout.
• address_line_2 - Customer’s address line 2 (e.g., apartment, suite, unit, or building), if collected at checkout.
• address_city - Customer’s city, district, suburb, town, or village, if collected at checkout.
• address_country - Customer’s two-letter country code, if collected at checkout.
• address_country_name - Customer’s full country name, if collected at checkout.
• address_state - Customer’s state, county, province, or region, if collected at checkout.
• address_zip - Customer’s ZIP or postal code, if collected at checkout.
• phone_number - Customer’s phone number, if collected at checkout.
• business_number - Customer’s business/tax number, if collected at checkout.
• custom_fieldname - Custom form fields and submitted values at the time of checkout (e.g., custom_1, custom_2, etc.).

​

Form Submission webhooks

The following fields are sent to your third-party applications (e.g., Zapier) when a customer submits a form.

​

Base fields

• id - Unique identifier for the form submission
• form - Information about the form that was submitted:
  • id - Unique identifier for the form.
  • title - The title of the form.
• custom_fields - An object containing all custom field values, keyed by the custom field’s title rather than its handle.

​

Default Form fields

These fields appear at the top level of the payload only if the corresponding field is configured on the form.

• name - The submitter’s full name
• email - The submitter’s email address
• phone_number - The submitter’s phone number
• mobile_phone_number - The submitter’s mobile phone number
• address_line_1 - Address line 1 (e.g., street, PO Box, or company name)
• address_line_2 - Address line 2 (e.g., apartment, suite, unit, or building)
• address_city - City, district, suburb, town, or village.
• address_state - State, county, province, or region
• address_country - Two-letter country code
• address_zip - ZIP or postal code
• business_number - Business/tax number

​

Parsed name fields

If the form has a name field configured, the following additional fields are included:

• first_name - The submitter’s first name, parsed from the name field.
• last_name - The submitter’s last name, parsed from the name field.

​

Custom Form fields

• custom_1 through custom_150 - Custom field values, keyed by their internal handle (e.g., custom_1, custom_2, etc.). These appear at the top level only if the corresponding custom field is configured on the form. The value is whatever the submitter entered.