Several months ago I suggested to give your customers the ability to view the API Requests. But that did not transpire for various reasons.
Keap Support have the ability to report on the API Calls for the Legacy API Key. What should have been done was to provide an interface so that your customers could easily check on the usage whenever they wanted to.
Unfortunately your team have created the following workflow.
Customer speaks to Support to get the Report.
Support have to manually run the Report and reply back to the Customer.
Customer gets the Report and has no clue what it all means.
Customer has to either go to the Forums, speak to a Developer, or speak to a Partner to find out what could be using the Key.
You have provided documentation on what the Legacy API Key means, what changes to do for the code, etc. But you have not provided any documentation on what the API Calls or User Agents mean. Hence why I wrote the Identification Guide to help out.
If your customers had an interface to run the report, then additional descriptions could have been added to explain what the API Call means. The purpose being that it would help jog their memories, plus it would have reduced the number of the customers still using the Key. I understand that not everything can be explained, but you may have been in a better position now.
Pav, you seem surprised that keap is bungling every step of this. I’m not. I’m debating what to do, for now, I’m going to try to just update our headers to use legacy keys, to give me a few more months to decide what to do about this nonsense. We don’t benefit in any way from this fantasy of keap’s to be some full fledged crm, it’s a 100% loss for us, they should pay us to deal with their mess, it’s absurd. We don’t need anything involved with any part of this new stuff, we use what we need, and don’t need more, and I am certainly stressing to the clients to NOT get more involved or dependent on this company. A few phone calls from client to keap resulted in them agreeing with me that they were not competent at all. So that’s my base to make decisions from. They’ve already convinced me, now the matter is to find the path of least pain to me personally. All will be pain, but the trick is to find the one that is least pain.
What’s comical is I couldn’t even find a way to log out of their site to use a different login, but that’s why I avoid dealing with this stuff with a 10 foot, or rather, 10 mile pole if I can at all help it. Competent people can find ways to either make better APIs, that don’t need core changes, or to to seamlessly handle it behind the scenes if they have to. Your samples here are helpful, unlike all the excuses the staff are making, but that’s exactly what I expect from these guys.
Unless anything has changed, the Legacy API Key access will stop functioning today.
If your integration has stopped working, then check if your integration is listed in the Integrators page via the link below. This will tell if the vendor has updated their software to either use Service Account Keys or OAuth (Authorized Connections).
If your integration is not listed, then check the Identification Guide via the link below for further assistance. If they are not listed in there, then check with the vendor directly. If they are unable to help, then you will need to find an alternative solution.
If you have a custom developed script, then check with the developer to make the necessary changes. If they are not available, there are other developers in this community that maybe able to help out.