I'm making an authenticated call to /me:


But it's returning:

{"error_id":500,"error_name":"internal_error","error_message":"this error has been logged"}

My token and key are valid so not sure what's happening.

Any info on this? Perhaps a bug?

  • Well, yes this is a bug. It should be giving you a more sensible error, but it looks like you're sending ['access_token'] instead access_token; as in, you're actually sending [, ', and ]. Apr 30, 2012 at 20:34
  • Ah, my url decoding threw those characters in there and I didn't notice them. Thanks Kevin! May 1, 2012 at 8:51

1 Answer 1


The bogus error message has been fixed in the latest deploy (it now correctly reports an invalid_access_token).

As to why your request is malformed, refer to my comment above.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .