Hi Jones,

You'd pretty much have to iterate through every media id starting at 1 and going up to the id found on the /latest (/movie/latest for example) method. There will be gaps in the ids space and those ids will return a 404.

Hi Travis,

okay, thanks for that hint. But, isn't there a limit of calls to the API in a specific time? So if I'd call every id individually, wouldn't that take way to many hours?

Okay, now I saw in "/search/movie" the parameter search_type with the description: "By default, the search type is 'phrase'. This is almost guaranteed the option you will want. It's a great all purpose search type and by far the most tuned for every day querying. For those wanting more of an "autocomplete" type search, set this option to 'ngram'."

This means I don't need database behind my input field, but I can use this search for implementing an input field with autocomplete? If so, how many requests will be sent when a user types in his entry? Will there be a new request every character?

Okay, I've read that those API calls limits are based on IP, not api_key. So I don't think someone would crash that limit and it doesn't matter how many users are linked in at the moment.

Yes, you have all of the info correct. I actually made search a fair bit smarter a while back but never updated the docs. search_type is obsolete and won't change your results anymore. The search tries to handle the ngram and phrase searching automatically now.