Right now to get both the rental history and their ratings for those movies is two separate steps, it should be pretty easy to include the rating along with the rental history.
There is a lot of data we could provide with any request, but we had to normalize the API resources to some extent or risk making the responses larger than some applications would desire. The good things is, with the way the API is designed, you can fulfill almost any user need with two sets of sequential calls, one to get your list of titles, one set of parallel requests to get whatever title-centric user data you need, e.g. ratings, title states, etc.
We also have a number of performance improvements in the pipeline that will make the latency on these sequential calls better.
Right now to get both the rental history and their ratings for those movies is two separate steps, it should be pretty easy to include the rating along with the rental history.
Thanks!
Message edited by Kallahar 3 years ago
Michael Hart – 3 years ago
There is a lot of data we could provide with any request, but we had to normalize the API resources to some extent or risk making the responses larger than some applications would desire. The good things is, with the way the API is designed, you can fulfill almost any user need with two sets of sequential calls, one to get your list of titles, one set of parallel requests to get whatever title-centric user data you need, e.g. ratings, title states, etc.
We also have a number of performance improvements in the pipeline that will make the latency on these sequential calls better.