It looks like you are sending a malformed access token.
Vy*iWEzkfPKHAzx7PEtJcA%2529%2529 is not of the proper form and exhibits classic URI encoding corruption.
Valid tokens all seem to be 24 characters that end in
) is often encoded as
%29 by browsers depending on how you get it and/or cut and paste.
')' === decodeURIComponent ('%29')
%25 is the URI encoding of
%, so your token was double URI encoded. (That's two times too many. ;) )
When I send the same request, with a validly formatted token (which I have since deauthorized):
I get a valid result.
When I double URI-encode the token:
I get the same 500 error that you got.
Note: The links above show the proper full format. Obviously, they won't work for you since I deauth'd the token (to protect my account's virginity).
You can go to the doc page, fetch your own token, and plug it into the above links and it will work.
PS: At this moment, your base token (
Vy*iWEzkfPKHAzx7PEtJcA))) appears to still be valid. When I fetch the link:
I get a valid but empty result:
which suggests that there might be some security against token hijacking. :)