Closed Timmeeehh closed 1 year ago
If you're going to implement the new API release, will you include the new authentication method with the Personal Access Token? Or is that for after the beta release?
The new authentication method will be necessary as the API key will be depreciated at some point.
Note: After Personal Access Tokens and OAuth are no longer in beta, a deprecation timeline for User API keys will be announced. There will be a notice period of at least 12 months before the deprecation is enforced, per our deprecation guidelines. We recommend migrating as soon as possible - some new features (e.g., metadata API access) will be exclusive to personal access tokens and OAuth access tokens.
FYI: The authorization header format didn't change. You can just replace the api key with your personal access token right now when making calls and it works just fine.
Will look into this soon. Thanks for the heads up.
I can confirm that changing the API key to your personal access token works. That was easier than expected :)
I had some trouble finding where to create a token, though. That's here: https://airtable.com/create/tokens
Nice! Has anyone looked into integrating the Fields to merge on addition?
Yes. It will be in a new Airtable.net release next week.
Enhancements included in new release of 1.3.0.
Hi! Thanks for all the work in this project! Is there a project planned for implementing the new API Release? If so I would be happy to contribute.