API Objects


Handling multiple pages of results.

The Paging Info object

Since there are many connections between objects in The Entertainment Graph, all methods that return lists of MediaHound Objects take advantage of paging. That means you will get only a subset of results. If you need more, you can fetch more, one page at a time. If you wanted to request the next page, the parameter next inside the pagingInfo is a URL with all the original query parameters. The only thing that needs to be done is appending the currently used access token to the URL or setting an appropriate Authorization Header. If next is NULL, there are no more pages.

"pagingInfo": {
"next": String

Configuring PageSize

For most queries, including within the HQL JSON request objects, we accept the param pageSize. Below is an example of the request structure for a Relate call to show how pageSize fits into the picture:

"pageSize": Integer,
"factors": FACTORS_ARRAY,
"filters": FILTERS_OBJECT,
"components": COMPONENTS_ARRAY


pageSizeOptional Integer. Indicates the number of results to return per Page. Default is 10.
factorsRequired array. Please see Factors.
filtersOptional object. Please see Filters.
componentsOptional array. Please see Components.