# Need API dev

**URL:** <https://integration.keap.com/t/need-api-dev/93156>\
**Category:** API Q&A\
**Created:** [September 13, 2024, 3:03pm UTC](https://integration.keap.com/t/need-api-dev/93156 "2024-09-13T15:03:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Pav](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/pav/32/124_2.png) [@Pav](https://integration.keap.com/u/Pav)\
**Post date:** [September 13, 2024, 3:35pm UTC](https://integration.keap.com/t/need-api-dev/93156/2 "2024-09-13T15:35:00Z")

</div>

Hi @Kendall_Gjevre,

For your reference, I have written a guide to help out in identifying Legacy API Key connections.

> [@Legacy API Key - Identification Guide](https://integration.keap.com/t/legacy-api-key-identification-guide/93019):
>
> February 2025 On February 14th 2025 Keap removed the use of the Legacy API Key. If your integration was using the Legacy API Key, then you need to generate a Service Account Key in your Account, and use that Key instead. October 2024 On October 31st 2024 Keap required all Legacy API Key integrations to pass the API Key (Legacy API Key / Service Account Key / Personal Access Token) via the the HTTP Header. The Legacy API Key will carry on working until February 14th 2025. June 2024 On June 12…

You can cross reference the integrations in the guide to see if they are at risk. Although it is not 100% accurate given the fact many integrations were developed over the years, so some using the Legacy API Key will not be known about yet.

If your client have custom developed API scripts that were done several years ago, there is a chance they they are at risk of breaking.

Did you client get an email from Keap saying the number of API calls that were done in the previous 30 days?

If so how many were done? That will help to see if they are using it extensively or not.

---

_[View the full topic](https://integration.keap.com/t/need-api-dev/93156)._
