Custom Query (41 matches)

Current API access is too open, too loose.

Maybe it would be a good idea to move towards an improved API base:

-Better authentication (shared-key for clients + oauth or username/encryptedpass for users)

-URL-Based API (like Twitter, TheMovieDB) for simpler methods.

-MUCH improved tracking: API session, time spent in session, time left in session, quota status for searches, downloads, API limits like max items per search, etc.

Having this in the API would help clients auto-regulate, disable functionality, or pre-emptyively throttle or deny requests.

-Modularize the API in a way that allows for certain functionality to be disabled (standard response for disabled methods or modules) or throttled (modifying the "quotas" footer/header mentioned above).

-Seriously consider simplifying registration (even providing a method for creating accounts directly) so no anonymous access is allowed.

It will be very helpful if you can provide to developers, a small example movie, that we can download, and also include all its details, like calculated hash and the file size. It should also include the hash xml-rpc query, and the expected response that includes several matching subtitles.

Hi,

I am curious to know if we can search inside subtitles. I mean by entering a word, we can see its usage in different movie subtitles.

Thanks Sima Valizadeh