- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Feb 08, 2023 01:56 PM
Using the token creation endpoint returns a 201 status code upon successful request. I believe the standard dictates a 200 response. This is causing me issues as I am using a popular OAuth nodejs library that rejects the Airtable token response because it's 201 and not 200. I'm implementing OAuth for many different providers and if I want to support Airtable I'll need to find another more lenient library for this one specific API. Ideally your authorization server would return a consistent response 😊

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Feb 28, 2023 01:04 PM
Hi @alarner, thank you for flagging this!
We will be fixing the token creation / token refresh endpoints to return 200 instead of 201 in the coming weeks, considering this change as a bugfix (i.e. not a breaking change). However, to avoid potential disruption, we'll be updating the documentation & sending an email notice to active OAuth developers ahead of time. I'll update this thread when the change has been rolled out.

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Mar 30, 2023 04:52 PM
Hi @alarner - this change has been rolled out (successful token creation / refresh returns 200 instead of 201)
