Soporte de The Movie Database

Hi, We are a startup based out of India. We have gone through your API pages,FAQs & other apps using your API. We loved you API & wanted to use for our app. We have gone through your FAQ section & API pages however we still have few queries.

These are mainly related to 3 points A. Modification of API (Hiding of certain parameters) in order to maintain consistency. B. Merging of our content with yours (Mainly for regional movies) C. Is there any provision to modify data( hiding some fields)? such as crew data?

Please find below mentioned detailed comments for your reference.

  1. We have our database for Indian regional languages so is to okay if we merge it with your database??? (by merging we mean using your data along with our data. Eg. Some Telugu movies are available in your database we can combine those with movies available with us)
  2. We are currently showing only 3 Genres for the movies & when we browse through some movies on TMDB, we found out that for some movies there are more than 5 genres so is it okay if we show most relevant 3 on our APP to maintain consistency? (Eg For wonder woman there are 5 genre Action, Adventure, Fantasy, Sci-fi while in our app we have different genres) Same applies with the artists as we are only showing top 8 artists of any movie so is it okay if we hide details of other artists?
  3. Is there any provision to use only artist pictures & details?

We wrote an email to you however we are still awaiting reply for the same so posted these basic doubts here, it'd be great if you could help us with the same.

Warm Regards, Akshay

4 respuestas (en la página 1 de 1)

Jump to last post

Hi Akshay, sorry for the late reply.

We have our database for Indian regional languages so is to okay if we merge it with your database?

Yes, it's fine to merge the data but the one clause in our terms to be aware of is 1B, you shall not "Sell, lease, or sublicense TMDb APIs or access thereto or derive revenues from the use or provision of TMDb APIs, whether for direct commercial or monetary gain or otherwise, except as set forth below."

So depending on what you're doing with the data and your company, it might not be so easy.

We are currently showing only 3 Genres for the movies & when we browse through some movies on TMDB, we found out that for some movies there are more than 5 genres so is it okay if we show most relevant 3 on our APP to maintain consistency?

Absolutely.

Is there any provision to use only artist pictures & details?

We don't distinguish any difference between what data you use, you can use whatever you want.

Hi Travis,

First of all thank you very much for your guidance.

It cleared most of our doubts, we wanted to ask few things, we had dropped a mail regarding the same but there is no reply so now we are again replying in this thread.

Just a few more queries regarding our future plans as well.

In our Mobile App, We are planning to use TMDB's API to display Artists pictures & details and in the future we are planning to give ratings for them. As of Now, we have no clue whether we can go ahead with this plan using TMDB's API, that's why we would like to know:

If we can go ahead with this plan of rating? If yes, does the API provide unique ID's for all artists/movies/etc? If there is any pricing involved here then how does it work? If IDs are available for our use, Can we use those ID's to map the ratings in our DB? (Here we would have to save/map those ID's in our DB so that our system can distinguish artists and their respective ratings.) Most Importantly regarding the clause in 1B of your Terms of use,

"Sell, lease, or sublicense TMDb APIs or access thereto or derive revenues from the use or provision of TMDb APIs, whether for direct commercial or monetary gain or otherwise, except as set forth below." By providing us their valuable ratings, we were planning to reward the users with offers. Does this come under the above clause?

By our understanding, this clause is applicable in that case when TMDB's API is used to display information and there are "Booking" options available on that same app/web application? Please correct if we are wrong. Again, If pricing is involved in the above two scenarios, how does it work out? Kindly help us out with these queries.

Warm Regards, Akshay Defaultx72@gmail.com

Hi Akshay,

Sorry for the radio silence. It's been hard for me to find time to get through all of my email.

If we can go ahead with this plan of rating? If yes, does the API provide unique ID's for all artists/movies/etc?

We only have a single rating, our "User Score" as it were. Is that what you are referring to? If so, yes you can use that. With regards to ids, obviously all of our own objects have ids and with regards to external ids there's a small assortment available. We have a document outlining which ids are available here.

If there is any pricing involved here then how does it work? If IDs are available for our use, Can we use those ID's to map the ratings in our DB? (Here we would have to save/map those ID's in our DB so that our system can distinguish artists and their respective ratings.)

There is no fee, we don't charge for any part of the TMDb service and yes, you can use the ids.

By our understanding, this clause is applicable in that case when TMDB's API is used to display information and there are "Booking" options available on that same app/web application? Please correct if we are wrong. Again, If pricing is involved in the above two scenarios, how does it work out? Kindly help us out with these queries.

I think the main point about 1B is the selling/leasing of the data. Simply showing some ads is neither of those things so you don't have to worry about it in that case. Are you going to be creating your own API/service where you resell data from TMDb?

Hi Travis,

Thank you for your time & guidance!

We only have a single rating, our "User Score" as it were. Is that what you are referring to? If so, yes you can use that.).

By user score we mean, we have separate user score(ratings) for Movies & stars. So consider example of "Spider-Man: Homecoming", in our app we have separate overall user score for Spider-Man: Homecoming along with individual scores for actors like Tom Holland, Michael Keaton, Zendaya & so on.

I think the main point about 1B is the selling/leasing of the data. Simply showing some ads is neither of those things so you don't have to worry about it in that case. Are you going to be creating your own API/service where you resell data from TMDb?

No, our app is in "Reviews, ticket bookings & analysis" segment & we are not planning to create any API or services to sell TMDB data. We are using artist & movie information available on TMDB for identification purpose only (by identification we mean in above case of Spider-Man: Homecoming, we will use Tom Holland's information like image, bio available on TMDB to tag him in our app)

Warm Regards, Akshay Defaultx72@gmail.com

¿No encuentras una película o serie? Inicia sesión para crearla:

Global

s centrar la barra de búsqueda
p abrir menú de perfil
esc cierra una ventana abierta
? abrir la ventana de atajos del teclado

En las páginas multimedia

b retrocede (o a padre cuando sea aplicable)
e ir a la página de edición

En las páginas de temporada de televisión

(flecha derecha) ir a la temporada siguiente
(flecha izquierda) ir a la temporada anterior

En las páginas de episodio de televisión

(flecha derecha) ir al episodio siguiente
(flecha izquierda) ir al episodio anterior

En todas las páginas de imágenes

a abrir la ventana de añadir imagen

En todas las páginas de edición

t abrir la sección de traducción
ctrl+ s enviar formulario

En las páginas de discusión

n crear nueva discusión
w cambiar el estado de visualización
p cambiar público/privado
c cambiar cerrar/abrir
a abrir actividad
r responder a la discusión
l ir a la última respuesta
ctrl+ enter enviar tu mensaje
(flecha derecha) página siguiente
(flecha izquierda) página anterior

Configuraciones

¿Quieres puntuar o añadir este elemento a una lista?

Iniciar sesión