Hi Maximilian,

The images section of the documentation make it pretty clear, doesn't it?

Regarding your specific question about whether data changes, yes it has. I don't think it's something you need to check super often but once every few weeks kind of thing would be smart. I'm here to help you not shoot yourself in the foot so it's advisable to check it. But it's 100% your call, haha.

Yup! I guess I missed that section, my bad. and is there any reason for the url to change?

No problem!

Now days, it probably won't change again but it has changed a total of 3 times since 2009. The last time was in 2014. I don't expect it to change again but that is why it's part of the config data. Just in case we ever had to emergency change it with little notice.

Great, thanks for the speedy replies. Another kind of issue I have a question about. So in my app, I would make a search request to Trakt, or get an actors movies/show credits they are in, and with that also get poster URLs for each. So in search for example, I only have to make 1 request for the search, then n requests based on the number of results to get the actual image. I'm sure its beneficial to you if I keep my requests down, but if I continue getting the data and ID's from Trakt, I would then have to make a separate request to TheMovieDB to get the image information, then the actual request for the image. Don't know if this would be possible or not, but could a API method that takes in a image size, and a show/movie/episode/season/actor ID and then pass back either the default image, or a constructed URL to the image? That would also solve the issue of caching and fetching a new image base URL, and cut down extra requests just to get the default images and banners used on the site.

Unfortunately I don't have anything planned like that at this time.

The problem for me when thinking about what you're asking for is that images are probably the single most expensive service we run and so having a user who only grabs images and doesn't otherwise contribute to what we're building here isn't as valuable as those who do. We give our service away for free and in exchange for that, we expect those users/developers/applications to send users back to us to build our database.

Images are crazy expensive at this scale but for us it's still worth providing since most of our users do a good job of helping to keep that balance.

Sorry if I got a little side tracked there, I just wanted to bring up a larger scale issue I have with tailoring parts of our service to users who only want images.

Cheers.

Well since I am using your service, I could maybe implement a user-sync in the app, but since the entire app is already built upon Trakt, and works nicely, it's an even bigger job to migrate it all over. The main thing I need are the images, (and if added sync, then user functions as well) but since I get info like episode names and descriptions and all that already, that's why I'm trying to keep the requests down so you don't have to serve extra information.

And since I'd be using the images I'd be helping add images for new shows if none are available.

Yup, for sure. I didn't mean to sound rude or anything even if it came out a little like that. I just meant to outline the general issue with implementing that specific feature so you have some background.

I completely understand where you're coming from, having to migrate everything is not something you're planning and hey, as long as TMDb is still attributed as the source for images, have at it.

I'll think about it some more but it's probably not something I'm going to be too worried about for now. I'm in the midst of planning our next gen (v4) API so who knows, maybe something like this could end up on being released.

Thanks for adding some input.

API Request: Anticipated TV Shows and movies. For some things I'd like to move to TheMovieDB API. Mainly because of the image thing, it seems crazy to get trending/popular/anticipated, then fetch from here just to get a image path, would be great to just use the API for all of that data as well.

Hi Maximilian,

Just so I can understand what you're expecting when we use the word "anticipated", what exactly are we talking about? The most popular items that have yet to be released? You can build that list on your own with discover. But if it's something else than let me know.

Hey Travis,

Looks good. Sorry about that! Just quickly trying to see what I might need and would think it's best to get API suggestions to you ASAP. I'll try to get familiar with the current API soon (making a API wrapper for it too) and let you know. Thanks for being patient, I wasn't expecting this sudden change, just freaking out a bit.

Did you receive my email as well?

Best, Maximilian Litteral

Ok, great no worries. If you have any more questions, fire away.

Did you receive my email as well?

Yes, I did. I'll reply to it in a bit here, just catching up from a holiday weekend ;)