Outbound Webhooks: What information am I sending?

Find out the fields sent to your third-party applications when you use Kajabi's Outbound Webhooks.

In this article:

• Outbound Webhooks
• Purchase Created Webhooks
• Payment Succeeded 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 multiple-payment 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
• custom_<fieldname>
  Custom form fields and submitted values at the time of checkout

Affiliate fields (if applicable)

• conversion_id
  Unique identifier for the affiliate conversion.
• user_id
  Unique identifier for the affiliate user.
• user_name
  Name of affiliate user
• user_email
  Email of affiliate user

Opt In

• opt_in
  Boolean representing customer opting in to email subscriber list at the time of checkout

Trial

• trial
  Boolean representing if the customer entered a trial period at the time of checkout

Transaction fields

• id
  Unique identifier for the transaction.
• created_at
  Date and time at which the transaction was created.
• offer_type
  Kajabi Offer type. Can be a one-time, subscription, multi-pay, or free Offer.
• subtotal
  Transaction amount, in currency's smallest currency unit, before discounts and taxes are applied.
• subtotal_decimal
  Transaction amount before discounts and taxes are applied. Formatted with decimal places if applicable.
• discount_amount
  Discount amount, if applicable, in currency's smallest currency unity.
• discount_amount_decimal
  Discount amount, if applicable, in currency's smallest currency unit. Formatted with decimal places if applicable.
• amount_paid
  Amount paid, in currency's smallest currency unit, after discounts and taxes are applied.
• amount_paid_decimal
  Amount paid after discounts and taxes are applied. Formatted with decimal places if applicable.
• currency
  Three-letter ISO currency mode.
• payment_method
  Payment method used for the transaction. For Kajabi Payments, this detail is more granular, such as visa, mastercard, apple_pay, etc.
• payment_processor
  Processor used for a particular transaction.
• coupon_code
  Coupon code, when applicable, used to calculate a discount.
• quantity
  The quantity of the item purchased.
• Subscription_id
  Unique identifier for the new subscription created.
• subscription_created_at
  Date and time at which the subscription of multiple payment was created.
• interval_payment_amount
  For recurring payments, this is the amount that is charged at the billing interval.
• payment_amount_decimal
  For recurring payments, this is the amount that is charged at the billing interval. Formatted with decimal places if applicable.
• interval_count
  Combined with interval, this is the frequency of billing. For example, interval_count = 2 and interval = week means the customer would be billed every 2 weeks.
• interval
  For recurring payments, this is the billing interval. For example, this can be week for weekly billing.trial_period_days
  For subscriptions, this is the number of trial days before billing starts. Can be between 1-365 days or null if not relevant.
• setup_fee
  For recurring payments, this is the amount charged immediately upon purchase. Can be used to create a paid trial.
• setup_fee_decimal
  For recurring payments, this is the amount charged immediately upon purchase. Can be used to create a paid trial. Formatted with decimal places if applicable.
• total_payment_count
  For multiple payments, this is the total number of installment payments.

Recurring payment fields (if applicable)

• Subscription_id
  Unique identifier for the new subscription created.
• subscription_created_at
  Date and time at which the subscription of multiple payment was created.
• interval_payment_amount
  For recurring payments, this is the amount that is charged at the billing interval.
• payment_amount_decimal
  For recurring payments, this is the amount that is charged at the billing interval. Formatted with decimal places if applicable.
• interval_count
  Combined with interval, this is the frequency of billing. For example, interval_count = 2 and interval = week means the customer would be billed every 2 weeks.
• interval
  For recurring payments, this is the billing interval. For example, this can be week for weekly billing.trial_period_days
  For subscriptions, this is the number of trial days before billing starts. Can be between 1-365 days or null if not relevant.
• setup_fee
  For recurring payments, this is the amount charged immediately upon purchase. Can be used to create a paid trial.
• setup_fee_decimal
  For recurring payments, this is the amount charged immediately upon purchase. Can be used to create a paid trial. Formatted with decimal places if applicable.
• total_payment_count
  For multiple payments, this is the total number of installment payments.

Payment Succeeded Webhooks

The following fields are sent to your connected third-party applications when a customer successfully purchases an offer, as well as for and subsequent successful payments for subscription and multiple payment offers. This also includes cart orders.

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, multi-pay, 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 a particular transaction, e.g., “Kajabi Payments”
• payment_method
  Payment method used for the transaction.  For Kajabi Payments, this detail is more granular, such as visa, mastercard, apple_pay, etc 
• sales_tax
  The sales tax, in the currency’s smallest currency unit (e.g., cents)
• sales_tax_decimal
  The sales tax included in the transaction.  Formatted with decimal places if applicable
• currency
  Three-letter ISO currency code
• amount_paid
  Amount paid, in currency’s smallest currency unit, after discounts and taxes are applied
• amount_paid_decimal
  Amount paid after discounts and taxes are applied.  Formatted with decimal places if applicable
• subtotal
  Transaction amount, in currency’s smallest currency unit, before discounts and taxes are applied
• subtotal_decimal
  Transaction amount before discounts and taxes are applied.  Formatted with decimal places if applicable.
• discount_amount
  Discount amount, if applicable, in currency’s smallest currency unit
• discount_amount_decimal
  Discount amount, if applicable, in currency’s smallest currency unit.  Formatted with decimal places if applicable
• coupon_code
  Coupon code, when applicable, used to calculate a discount
• quantity
  The quantity of the item purchased
• fee_amount
  Fee amount applied to the transaction in the smallest currency unit (e.g., cents)
• fee_amount_decimal
  Fee amount in decimal format (e.g., euros)
• net_amount
  The net amount after fees and discounts in the smallest currency unit (e.g., cents)
• net_amount_decimal
  The net amount in decimal format

Recurring payment

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

• id
  Unique identifier for the recurring payment.  This can either be the subscription ID or multiple payments ID.
• created_at
  Date and time at which the subscription or multiple payment was created.
• payment_amount
  Amount, in the currency’s smallest currency unit, that is charged at the billing interval.
• payment_amount_decimal
  Amount that is charged at the billing interval.  Formatted with decimal places if applicable.
• interval
  This is the billing interval.  For example, this can be a week for weekly billing.
• interval_count
  Combined with the interval field, this is the frequency of billing.  For example, interval_count = 2 and interval = week means the customer would be billed every 2 weeks.
• trial_period_days
  For subscriptions, this is the number of trial days before billing starts.  Can be between 1-365, or null if not relevant.
• total_payment_count
  For multiple payments, this is the total number of installment payments.
• payments_made
  For multiple payments, this is the total number of payments made.
• setup_fee
  This is the amount charged immediately upon purchase. Can be used to create a paid trial.
• setup_fee_decimal
  This is the amount charged immediately upon purchase. Formatted with decimal places if applicable.

Affiliate 

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

• conversion_id
  Unique identifier for the affiliate conversion
• user_id
  Unique identifier for the affiliate user
• user_name
  Name of the affiliate user
• user_email
  Email address of the affiliate user

And that's the Outbound Webhooks sent by Kajabi! Please vote below and let us know if you found this article helpful. We value your feedback. Thanks for being the best part of Kajabi!