دعم الموقع
الدعم → دعم API
Intended use case for accessing the API, server or client side?
نشر بواسطة johnb003STAFFMOD في يوليو 24, 2013 عند الساعة 5:08 مساءا
I noticed the limit on API requests is limited per IP not per API key. If my app gets a lot of traffic then it seems like this would suggest my requests should all come from my users instead of from my server.
However, if I generate the request from the client, how can I protect my API key?
Thanks!
رد بواسطة Travis Bell
بتاريخ يوليو 24, 2013 في 6:49 مساءا
Hi johnb003 ,
It depends what kind of client you are building. For any desktop or mobile application, your API key can be compiled in to your app and would never be visible to the public. If you're building an HTML based project, there isn't much of a way to obfuscate it. Make a note that API keys are free and to head over to TMDb to get one is the best you can probably do.
رد بواسطة johnb003
بتاريخ يوليو 24, 2013 في 7:58 مساءا
It's for http, and mobile. Is it ok if I maintain a clone of the db, as long as I don't cache the images? I didn't find anything in the Eula that prevented this, but I guess it's good to double check.
After all you do have the changes api which makes it very nice and convenient to maintain such a clone.
رد بواسطة Travis Bell
بتاريخ يوليو 25, 2013 في 10:23 صباحا
As long as you attribute TMDb as the source of the data you're fine to go ahead and do that.