Hey, my app was using the /4/account/{account_object_id} route to get info about and to verify an user that has logged in to my app using their tmdb account. However, it seems like the route does not exist anymore (I'm getting 404 "The resource you requested could not be found.", with status code of 34, same response as for non-existent route.) Was there perhaps changes made to the v4 api? If so how does one verify a sessionId for a logged in user (v4) and fetch their name based on their v4 user object id? Also there doesn't seem to be much documentation surrounding this, apart from a couple of posts in this forum.
I appreciate what you guys do here, cheers!
¿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 1 de agosto de 2024 a las 12:11
Hey @aleksilassila,
Good catch! This route was missed during a migration a month or two ago.
I'll get this fixed up this morning, thanks.
Contestado por Travis Bell
el 2 de agosto de 2024 a las 12:54
I've restored the original
/4/account/{account_object_id}
route, you should be seeing responses there now.Thanks.