Stack Overflow Users Batch API
Up to 100 user ids per request, one profile per distinct id, in the order you sent them.
GET /v1/stack-overflow/users/batch1 credit per user id Up to 100 ids per request Max 100 credits An id that is not a user is still charged Failed requests are free
About this endpoint
GET /v1/stack-overflow/users/batch?ids=22656,1 answers one entry for every distinct id, in the order first asked. Each entry has id, its own lookupStatus and user, which is null for a miss. A mix of existing and missing ids is a normal 200 response.
The batch charges 1 credit per distinct user id, including an id that does not exist, and repeats are dropped before billing. -1 is the Community user and is accepted. For one id, the single user route returns the same profile shape.
Stack Overflow Users Batch API FAQ
How many user ids can one call take?
1 to 100 ids, comma-separated. Duplicates are dropped before the request and before billing.
How is the batch billed?
Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.
Does the order of entries match the ids?
Yes. data.users has one entry per distinct requested id in the order first asked, and each entry repeats its id.
What happens when one id is missing?
Its entry has lookupStatus not_found and user null, while the rest carry their profiles. The response stays HTTP 200.
Other Stack Overflow endpoints
- QuestionGET /v1/stack-overflow/questions/{questionId}
- Questions by idGET /v1/stack-overflow/questions/batch
- QuestionsGET /v1/stack-overflow/questions
- SearchGET /v1/stack-overflow/questions/search
- Similar titlesGET /v1/stack-overflow/questions/title-search
- AnswersGET /v1/stack-overflow/questions/{questionId}/answers
- CommentsGET /v1/stack-overflow/posts/{postId}/comments
- Comments by postGET /v1/stack-overflow/posts/comments