![]() Many partners have already implemented OAuth - here are guides written by Zapier, Make, and Fivetran on how to migrate your usage. If you are unsure how to set up OAuth for a specific partner or OAuth is not currently available for that partner, we recommend you contact their team for details on when it will be available. Airtable Data Sync to Hubspot)Ĭustom integrations & data connections should be updated to use personal access tokens, while third-party integrations, extensions and plugins require you to re-authorize using OAuth. ![]() Data Fetcher)Īirtable plugins for other apps (e.g. Third-party marketplace extensions that requested your Airtable API key (e.g. No action is required on your part until they complete the migration, after which you can stop using your API key and use OAuth to connect instead. Note: We are working with third-party integrations to migrate to using OAuth for integrations. Third-party integrations you have connected your Airtable account to (e.g. Tableau web data connector, Power BI & Power Query) To find out what is using your API key, we recommend checking the following:Ĭustom integrations set up by you or developers on your teamĭata connections and scripts that use your Airtable data (e.g. Developers can also create multiple personal access tokens for different API integrations, rather than having one API key used by multiple integrations. This is a benefit of using OAuth for integrations - you will be easily able to view and manage your authorized OAuth integrations, and any activity coming from integrations will be attributed to the specific integration. Unlike our new authentication methods, Airtable is not able to determine what is using your API key or who you may have shared your API key with in the past. Mid-February 2023: We will email API key owners with recent API key usage to directly inform them of the changesĪugust 1st, 2023: Users can no longer create new API keysįebruary 1st, 2024: Existing API keys can no longer be used to access the Airtable API January 2023: Initial community forum announcement and emails We recommend that all users migrate to Personal Access Tokens for individual use and OAuth for third-party integrations moving forward. Webhooks created with User API keys will not expire, but can no longer be created. Review that section for more details about where you may have used your API key.Ĭonnecting Airtable with third-party integrationsĪPI key deprecation details and timeline DetailsĪs this is a major change to the Airtable API, the API Key deprecation period will last for 12 months and end on Feb 1, 2024.Īfter that date, API Keys will no longer be able to access the Airtable API. As mentioned in the How can I find what is using my API key section, Airtable is NOT able to identify the particular bases that are using an API key. Please reference the below table for a summary of what may be impacted. If you've added your Airtable API key to 3rd party tools like Zapier, Make, etc. ![]() Both of these methods offer more granular control of resources and scopes and enable both developers and end-users to extend Airtable while ensuring the highest grade of security. API keys are being deprecated in favor of the two new API Authentication methods. This article serves as the announcement of the beginning of the deprecation period for API Keys. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |