It would be a huge overload for the server (and most of the clients)
to always return all posts. So, the API provides two mechanisms to
iterate through all posts:
- either page based (from latest to oldest):
you'll have to provide the page=<page_number> parameter (as in /api/2/
users/me/sites/<'primary' or id>/posts?page=<page_number>
- last retrieved post (from oldest to latest):
you'll have to provide the since_id=<last_retrieved_post_id> parameter
(as in /api/2/users/me/sites/<'primary' or id>/posts?
since_id=<post_id>)
The documentation would do a better job if it would provide a
description of:
- the result format
- the max number of posts returned by each of these requests
:- alex