Hello,
I am a little confused about the process of session IDs. I understand that the request token expires in 60 minutes, but once the request token is accepted and a session ID is granted, does that have an expiry?
If not, would that act as the user's persistent access to the ability to use the services of TMBD's API?
I am trying to build an app and I am trying to understand how to give the user persistent access once they have signed up. I was wondering if they have to go through the process of getting a request token and new session ID every time they login, or is the session ID to be saved and used on all future logins? It seems it would not be very user friendly to have to be redirected upon every login. I know that letterboxd uses TMDB's API to some extent, and I do not have to keep granting permission, so I am assuming there is a way to do this.
Thank you.
Can't find a movie or TV show? Login to create it.
Want to rate or add this item to a list?
Not a member?
Reply by superboy97
on January 30, 2024 at 1:30 AM
Letterboxd use the TMDB's API only to get the data of the movies and/or series. After that, they work only on their own site. So, no session Id are needed.
Reply by stefk13
on January 30, 2024 at 1:34 AM
Okay, thank you for the clarification on that. Would you happen to know the answer to my question about whether persistent authentication is feasible through TMBD, or would the user have to be redirected and accept every time?
If no session ID is needed because they use their own site, would it then be possible for my application to also just use the main API key server side for anyone requesting movie data and we handle the rest?
Reply by superboy97
on January 30, 2024 at 2:02 AM
I don't know.
Yes. This is the way most of the applications are working. sessionId are only needed if you want to give your users the possibility to change their own data on the TMDB site.
Reply by stefk13
on January 30, 2024 at 2:14 AM
Thank you!