# 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:** 1\
**Showing post:** 3

<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

---

_[View the full topic](https://community.hubspot.com/t/have-a-second-api-key/18234)._