# Have a second API KEY

**URL:** <https://community.hubspot.com/t/have-a-second-api-key/18234>\
**Category:** APIs & Integrations\
**Tags:** companies, workflows, developer-tools, oauth, forms, object, contacts, webhooks\
**Created:** [January 21, 2020, 9:40am UTC](https://community.hubspot.com/t/have-a-second-api-key/18234 "2020-01-21T09:40:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gbe](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/gbe/32/35926_2.png) [@gbe](https://community.hubspot.com/u/gbe)\
**Post date:** [January 21, 2020, 9:40am UTC](https://community.hubspot.com/t/have-a-second-api-key/18234/1 "2020-01-21T09:40:32Z")

</div>

Is there a way (even temporarily) to get 2 API Keys?

We have lots of integration, and we are not abe to rotate the key on all of them, without a significant downtime.

I don’t find any way on the API Key settings, nor in the documentation:[Authentication overview - HubSpot docs](https://knowledge.hubspot.com/integrations/how-do-i-get-my-hubspot-api-key)

I have seen other post asking for mutliple API Keys (one per integration) or with finer grain permission. That would be even better, but this request is much more humble, so might be trivial to implement from your R&D.

---

<div class="post-metadata">

**Author:** ![Willson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/willson/32/84663_2.png) [@Willson](https://community.hubspot.com/u/Willson)\
**Post date:** [January 21, 2020, 2:42pm UTC](https://community.hubspot.com/t/have-a-second-api-key/18234/2 "2020-01-21T14:42:21Z")

</div>

Hi @gbe

This is a regular request we see quite often but something we’re not currently supporting.

We do have this added as a feature request on our Ideas Forum and so i’d recommend heading over to this post to upvote this request:

[https://community.hubspot.com/t5/HubSpot-Ideas/HAPI-Key-Security/idi-p/255492](https://community.hubspot.com/t5/HubSpot-Ideas/HAPI-Key-Security/idi-p/255492)

---

<div class="post-metadata">

**Author:** ![CBN](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/cbn/32/95196_2.png) [@CBN](https://community.hubspot.com/u/CBN)\
**Post date:** [August 25, 2021, 2:48pm UTC](https://community.hubspot.com/t/have-a-second-api-key/18234/3 "2021-08-25T14:48:29Z")

</div>

Hello @Willson ,

This is VERY unfortunate as we may end up with gaps in our integration.

Normally you would have a grace period for the old key which would give you e.g. 24 hours to get all related systems updated. We cannot just release a new version and HOPE that nothing happens during the interval from where the key is changed in HubSpot and then it is deployed with our own app.

Please contact me in case you want to know how these things work in the real world and not in your lab.  
Thanks.

Christian

---

<div class="post-metadata">

**Author:** ![JBonfante](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jbonfante/32/194183_2.png) [@JBonfante](https://community.hubspot.com/u/JBonfante)\
**Post date:** [March 28, 2022, 6:14am UTC](https://community.hubspot.com/t/have-a-second-api-key/18234/4 "2022-03-28T06:14:15Z")

</div>

Is this technically a soltuion?

---

<div class="post-metadata">

**Author:** ![Lauren\_D](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/lauren_d/32/43872_2.png) [@Lauren\_D](https://community.hubspot.com/u/Lauren_D)\
**Post date:** [October 26, 2021, 1:13pm UTC](https://community.hubspot.com/t/have-a-second-api-key/18234/5 "2021-10-26T13:13:45Z")

</div>

Agree with GBE and cbn. Our development team is scratching their heads on why this is so different than every other integration. We were told to “have all of the pages open at once” but no system updates instantaneously, so this suggestion does not solve the issue at all. Downtime = lost revenue and frustration for potential and current customers. We now have to wake up in the middle of the night to deploy changes across our entire system as the best attempt at minimizing down time 😞 Please address this!
