Skip to main content

Infusionsoft API update [Action Required if you're using the Unbounce/Infusionsoft integration]

  • 20 January 2025
  • 1 reply
  • 21 views

Quinn_Omori
Unbouncer
Forum|alt.badge.img+1

Hey y’all,

Quinn from Unbounce here.

If you’re a Keap/Infusionsoft user, you probably already know that they’ve updated their legacy API and are set to deprecate it in February of this year. To make sure the Unbounce → Infusionsoft integration keeps working, we’ve made an update to migrate from the legacy API to Keap’s new Service Account Keys (SAKs).

If you’re using the integration, you’ll need to take action to complete the migration for your specific Unbounce account.

Please follow the steps below to Re-authenticate your Infusionsoft integration. The re-authentication will be applied to all pages using the Infusionsoft integration per Client, which means if you have multiple clients, you’ll need to Re-authenticate your Infusionsoft integration on one page in each Client in your account.

  1. Navigate to the Page Overview of an Unbounce page that has a configured Infusionsoft integration
  2. Click Integrations on the left side panel
  3. Click on the integration to open up the Infusionsoft integration modal
  4. Click on the "Re-authenticate using Service Account Key" link to navigate to the list of Infusionsoft Authentications
  5. Click on the "Re-authenticate" button to update the Authentication's Legacy API key to the new Service Account Key
  6. Enter the Service Account Key created on the same Infusionsoft/Keap account as the existing Legacy API Key
  7. Click on the "Authenticate with Infusionsoft" button
  8. Verify that the new Service Account Key is successfully validated and updated

If you have any questions or need assistance please reach out to us via the Support widget near the top right of the Unbounce app and one of our lovely Support Coaches will be able to lend you a hand (with this or anything else).

Cheers!
 

adamfinch
Quinn_Omori wrote:

Hey y’all,

Quinn from Unbounce here.

If you’re a Keap/Infusionsoft user, you probably already know that they’ve updated their legacy API and are set to deprecate it in February of this year. To make sure the Unbounce → Infusionsoft integration keeps working, we’ve made an update to migrate from the legacy API to Keap’s new Service Account Keys (SAKs).

If you’re using the integration, you’ll need to take action to complete the migration for your specific Unbounce account.

Please follow the steps below to Re-authenticate your Infusionsoft integration. The re-authentication will be applied to all pages using the Infusionsoft integration per Client, which means if you have multiple clients, you’ll need to Re-authenticate your Infusionsoft integration on one page in each Client in your account.

  1. Navigate to the Page Overview of an Unbounce page that has a configured Infusionsoft integration
  2. Click Integrations on the left side panel
  3. Click on the integration to open up the Infusionsoft integration modal
  4. Click on the "Re-authenticate using Service Account Key" link to navigate to the list of Infusionsoft Authentications
  5. Click on the "Re-authenticate" button to update the Authentication's Legacy API key to the new Service Account Key
  6. Enter the Service Account Key created on the same Infusionsoft/Keap account as the existing Legacy API Key
  7. Click on the "Authenticate with Infusionsoft" button
  8. Verify that the new Service Account Key is successfully validated and updated

If you have any questions or need assistance please reach out to us via the Support widget near the top right of the Unbounce app and one of our lovely Support Coaches will be able to lend you a hand (with this or anything else).

Cheers!
 

Thanks for the heads-up about the API migration. I’ll make sure to follow the steps to re-authenticate the integration using the Service Account Keys for each client. Always loving your timely support!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings