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.
Non riesci a trovare un film o una serie Tv? Accedi per crearlo.
Vuoi valutare o aggiungere quest'elemento a una lista?
Non sei un membro?
Risposta da superboy97
il 30 gennaio, 2024 alle 1:30AM
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.
Risposta da stefk13
il 30 gennaio, 2024 alle 1:34AM
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?
Risposta da superboy97
il 30 gennaio, 2024 alle 2:02AM
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.
Risposta da stefk13
il 30 gennaio, 2024 alle 2:14AM
Thank you!