Hey, I'm having problems with API v4, both from my code and from "Try it out" on the website. First I can't figure out why it requesting a String as account id since it should be a Number (maybe my fault, but I couldn't find a String id for accounts). Second I'm receiving a 500 error as I said in the title, I tried both with a String and with a Number, but I got the same result. I'm correctly authorizing my token and I thinks that's not the problem, since in that way it should return a 401 error.
If it could help, here is my library on GitHub: Repo.
Thank you. Davide.
¿No encuentras una película o serie? Inicia sesión para crearla:
¿Quieres puntuar o añadir este elemento a una lista?
¿No eres miembro?
Contestado por Travis Bell
el 3 de junio de 2018 a las 12:20
What's the request you are making that is throwing the 500 error?
Contestado por Davide
el 3 de junio de 2018 a las 12:29
All the requests I've tried for API v4, probably I'm mistaking the token Auth, I'm not very experienced ad that. With API v3, when the user allow the request the redirect uri include a new token, instead the API v4 should return an uri without params and must use the same token just created, right?
Contestado por Travis Bell
el 3 de junio de 2018 a las 12:34
You can use this little demo script I made to follow each step, 1, 2 & 3 to create a valid access token. It works correctly and allows you to inspect the responses. You can also inspect the code, it's all just client side JS.
Here's another little script that will let you get some of your account lists once you have a access token.
Contestado por Davide
el 3 de junio de 2018 a las 12:43
Got it, is about the accountId, I though it was my personal account ID (which is an integer ), I will let you know asap, I'm on smartphone now, thanks so much for now.
Contestado por Davide
el 16 de junio de 2018 a las 14:44
@travisbell sorry for the late answer, but it's a personal project I'm running in spare time, anyway it was my fault, you can close it 😊