Timeline for 400 Error when attempting to retrieve authenticated user data
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 19, 2012 at 21:12 | comment | added | rhinds | Hi @Kevin Montrose, I have just come back to this project (having been working on other things) - I have now updated my request to include the key (now hitting: api.stackexchange.com/2.0/me?site=stackoverflow&key=XXXXXXX) and including the access_token, but I am still getting the same "resulted in 400 (Bad Request)" Error - any other ideas or suggestions? | |
| Mar 26, 2012 at 17:35 | comment | added | rhinds | Great thanks - am going to try including my key in the request. | |
| Mar 26, 2012 at 17:13 | comment | added | Kevin Montrose | @rhinds - looks like a documentation oversight, I'll get it fixed in the next deploy. | |
| Mar 26, 2012 at 10:36 | comment | added | rhinds | Thanks - I thought that the key was only required in cases where the access token is not being passed - the only thing I can find in the docs about is this: "Pass this as key when making requests against the Stack Exchange API to receive a higher request quota." Is there any documentation detailing that it is required? | |
| Mar 23, 2012 at 16:35 | history | answered | Kevin Montrose | CC BY-SA 3.0 |