What You Need to Know About Keap
Sunsetting the Legacy API Key
The Legacy API Key is going away.
If you aren’t using the legacy keys – then this won’t affect you at all. You can stop reading and continue with your email marketing efforts.
If you do have other applications connecting with Keap using the legacy method, then it’s time to start looking into how those can be updated to use one of the other connection methods that Keap offers.
What is the Keap API?
API stands for Application Programming Interface.
An API is a set of rules or protocols that software (Keap) uses to talk with each other to exchange data. Virtually all software has one and they operate in the background without any active input from you.
If you have another piece of software that your business uses, and you want to be able to use it to pass information to Keap or receive information from Keap, then the API is generally how this would be achieved.
The API itself is not going away. It is a critical function required for Keap to share data with software that you use in your business – like your webinar, membership, or shopping cart software.
What is changing is the method that Keap is using to authorize those apps to communicate. The key is like master access to Keap – and the legacy version is not as secure as other methods of granting access.
So it’s got to go.
What are the Keap Legacy API Timelines?
June 7, 2024
Keap announces that they are sunsetting Legacy API Keys
July 10, 2024
Keap locks down the ability to create a Legacy API key.
August 5, 2024
Keap will begin a series of brownouts (intentional, planned disruptions of service). This may interrupt the function of your Legacy API (ad disrupt your business). This is something you cannot opt out of.
October 31, 2024
Keap sunsets the Legacy Key – they will no longer accept API calls using Legacy Key authentication. Your API connection with other apps and software will cease to work.
What Do I Need to Do?
It is the Legacy API Key that is going away.
If you are a new Keap user, this likely will not affect you as you are likely using one of the other (more secure) methods of authorizing the API.
But if you have connections depending on this method, then it’s time to start looking into how those can be updated to use one of the other connection methods.
Unfortunately, there is no easy way (in Keap) to identify which applications are connected by the Legacy API. You can contact Keap Customer Support they can give you a list of API calls made on your Keap account. It will take some detective work from that information.
Think of all the tools that share data with Keap – your shopping cart, webinar system, appointment booking, membership, elearning – all of these could be sharing data with Keap.
Check the configuration of each one to see how they are connected to Keap. If they use the Legacy API, change it to one of the below connection methods:
- Personal Access Tokens
- Service Account Keys
- Third-Party Authorizations
If you have a custom-built application or process that depends on the legacy API connection, you will need to contact the developer to make the necessary changes.
Do this well enough in advance that you know that the communication between keap and your third-party application is working – you don’t want to start losing data when Keap starts their “brownouts” in August!
Looking for peace of mind and less tech stress?
Security, performance, backups, privacy, and much more – the list of tasks needed to keep your website performing at its peak can seem overwhelming and time-consuming.
Signup for website management and get a tech-savvy team who are committed to your business.
Never worry about your website again.
Let Us Help You