The Movie Database Support
Support → API Support
Local Cache & Storage of API data
posted by Peter ScottSTAFFMOD on December 29, 2013 at 9:15 PM
Hello,
Before I proceed with programming my application (which is essentially a private mediahub), I was wanting to confirm that my planned usage is compliant with TMDb licensing. There is a clause in the terms of use for the api that is as follows: "You shall not... ...cache any TMDb metadata or photos other than for reasonable periods in order to provide your service."
However, local storage is supported in the api; for example, it is suggested that configuration data be stored locally and updated regularly. To avoid confusion, I will simply explain my planned usage.
My application will provide a private storage and streaming service for our dvd collection. In order to allow the application to work if our internet connection is offline, and to improve response speeds, I would like to store all information regarding the films in our collection in a local database and update it weekly or monthly. Live api requests would then be made when fetching information about any people or films outwith the dvd collection. This means that we would have long-term local storage of data. Is this an acceptable use of the TMDb api?
Reply by Travis Bell
on December 29, 2013 at 11:05 PM
Yes, that is fine. We encourage you to cache data locally.
The primary point of that clause if that you acknowledge that the data is not owned by you and should we request you to remove it, you are bound to do so. In 5 years we've never once had to ask anyone to do this but it's still our policy and terms that you need to agree to if you want to use our web service.
Cheers.
Reply by Peter Scott
on December 30, 2013 at 1:30 PM
Excellent, thank you.