# Airtable API Key deprecation
**URL:** https://community.glideapps.com/t/airtable-api-key-deprecation/65328
**Category:** Ask for Help
**Tags:** airtable
**Created:** [August 24, 2023, 6:42am UTC](https://community.glideapps.com/t/airtable-api-key-deprecation/65328 "2023-08-24T06:42:13Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@parisiam](https://community.glideapps.com/u/parisiam)
#### Post date: [August 24, 2023, 6:42am UTC](https://community.glideapps.com/t/airtable-api-key-deprecation/65328/1 "2023-08-24T06:42:13Z")
As you may know, Airtable API key are supposed to expire Feb 1, 2024.
[https://support.airtable.com/docs/airtable-api-key-deprecation-notice](https://support.airtable.com/docs/airtable-api-key-deprecation-notice)
Glide has set up a new way to connect to Airtable through OAUTH.
The context : I already have a functional application with an Airtable API connection and lots of data, screens and mechanism.
My problem : I’m afraid that by switching from API connection to OAUTH connection in my existing app with break the app (I don’t want to try an find out, I would be weeks of work to redo it)
My question is : How do I switch from Airtable API connection to the new OAUTH connection without breaking all the existing table integrations (and breaking my app) ?
Do I just add the OAUTH connection and remove the API connection (or let it die in Feb 2024) ? Has anyone did that already ?
PS: I’ve also seen this warning posted by Glide here :
[https://www.glideapps.com/docs/essentials/data-sources/airtable](https://www.glideapps.com/docs/essentials/data-sources/airtable)
It says: Airtable is experiencing OAuth integration issues for all of their third-party services. Airtable’s outage may prevent your Glide app from syncing to your Airtable base. To resolve this issue, the Glide team recommends reconnecting to your Airtable base with your Airtable API key.
Is this warning still valid ?
---
### Author:  [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [August 24, 2023, 11:35pm UTC](https://community.glideapps.com/t/airtable-api-key-deprecation/65328/2 "2023-08-24T23:35:03Z")
@Brett @Robert_Petitto can you help with this? Thank you.
---
### Author:  [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)
#### Post date: [August 25, 2023, 12:56am UTC](https://community.glideapps.com/t/airtable-api-key-deprecation/65328/3 "2023-08-25T00:56:44Z")
I don’t have an answer for this…I think a Glide Dev would need to weigh in.
---
### Author:  [@Brett](https://community.glideapps.com/u/Brett)
#### Post date: [August 25, 2023, 6:26pm UTC](https://community.glideapps.com/t/airtable-api-key-deprecation/65328/4 "2023-08-25T18:26:52Z")
Thank you - I asked the team.
You need to go through the OAuth process, then refresh the browser so the API key is removed. This should clear you up!
---
### Author:  [@parisiam](https://community.glideapps.com/u/parisiam)
#### Post date: [August 31, 2023, 5:06am UTC](https://community.glideapps.com/t/airtable-api-key-deprecation/65328/5 "2023-08-31T05:06:15Z")
Thank you all very much for your answers.
Just to be clear, is this the process I should follow :
- Step 1 : inside my app, I select Airtable as a data new connection
- Step 2 : I choose “Add another data connection” and select the same Airtable base I’m already connected to
- Step 3 : I connect to the Airtable base through OAuth
- Step 4 : I edit the current Airtable API key and delete it
Is this process ok ?
Or from what you say, @Brett, the Step 4 is not necessary ?
I have 5 other Glide applications linked to **the same Airtable base**.
Should I repeat the same process in each application ?
Or doing it in one app is enough ?
Thanks and regards,
---
### Author:  [@system](https://community.glideapps.com/u/system)
#### Post date: [September 7, 2023, 5:07am UTC](https://community.glideapps.com/t/airtable-api-key-deprecation/65328/6 "2023-09-07T05:07:06Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.