Getting 422 Unprocessable Entity response from GitHub Search API #139773
Replies: 1 comment
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
We're using search APIs authenticated via an OAuth application. Some of these APIs such as:
Are giving us a 422 response with the following message:
The query parameters of the request are as follows:
{'q': 'query_term user:username', 'per_page': 7}
The
username
is actually fetched by making an API call to/user
endpoint, so it's highly unlikely that the authenticated token doesn't have permission to view it's own user's data.Can anyone share more context if they've dealt with this error before? What could we be doing wrong?
Beta Was this translation helpful? Give feedback.
All reactions