When a client makes a request for a paginated resource, to construct the URL of the next page they need to find the “next_cursor_str” property of the response, add it to the query parameters as “cursor” (replacing any “cursor” value that’s already there), build a new query string and append that to the base URL.
It would be easier if the URL of the next page was returned in a Link HTTP header, using the standard “next” link relation.
Response HTTP header:
Link: https://api.twitter.com/1.1/friends/list.json?screen_name=invisiblecomma&count=20&cursor=1453698487262060565; rel=“next”
Would it be possible to add this header to paginated responses, when there’s a next page?