The Movie Database Support
Support → API Support
User Authorization flow for using both v3 and v4 endpoints
posted by Cinematics: The Movie GuideSTAFFMOD on March 5, 2017 at 10:48 PM
In my app, I would like to provide some of the list features found only on the version 4 endpoints. Is the expected flow to have the user authorize the app using the v3 endpoint to get a session id and then have the user authorize the app again for the v4 endpoint to get the access token? Or can I transition only to the v4 for authorization, and somehow use the access token to call the v3 endpoints?
Reply by Travis Bell
on March 5, 2017 at 11:09 PM
I have plans to introduce a migration system of a sort but haven't got to it yet. I have a ticket for this here, hopefully I'll find some time to get to this in the next little while.
Reply by Travis Bell
on July 24, 2018 at 12:40 PM
Hey there,
So I just pushed this live, and what I did was create a way to create a v3 session ID from a authorized v4 access token. You can read more about this method here: https://developers.themoviedb.org/3/authentication/create-session-from-v4-access-token
All of the account and media lists can be queried on v4 now but you still can't rate/add/remove account list items (rated, watchlist, favourite). This is still planned. But at least now if you start with a v4 access token, you can do all account actions whether it's a v4 of v3 method.