Hi, I am thinking about developing an android app that would use TMDb api. I have an api key which I would like to hard-code in order to make it easier for the user to start using the app right away. Since the cap for API calls is limited by the ip and not by the key, it seems like it might work. The problem is the personal lists. Are those lists linked to the api key or to the ip? If they are linked to the ip, then it's fine. But if the personal lists are linked to the api key then it's going to be a mess. I could store the lists locally but it's more tedious and the user won't be able to see those lists on a different device. So my question is: are the custom lists linked to the API key or to the IP address? And if they are linked to the API key what would be the best solution to the custom lists (and one API key)?
Edit: Just to make it more clear. All the users of this app would use the same API key.
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 Travis Bell
on October 25, 2015 at 10:36 AM
Hi corneliu,
Lists use session ids which are linked to user accounts. You can read more about sessions here.
Think of it like this, you use your API key to communicate with and be given access to the API. There are no user features with just an API key. If you want to do anything with a user account (rate items, create lists, add items to your watch list) you need to use a session id.
Cheers.
Reply by corneliu
on October 25, 2015 at 5:48 PM
Thank you Travis,
I think the first version will not use the session stuff as it requires the user to create an account with tmdb. At least in the beginning I want to make it as simple as possible for the user. So I guess I'll store the lists locally.