MailChimp API 3.0 is a RESTful solution to allow applications take action on MailChimp resources (e.g. “subscribers”, “campaigns”, "lists" etc.) using the standard HTTP methods: POST, GET, PATCH, and DELETE.
Within this API, pagination is enabled by default for some resources, which means HTTP GET calls only return the top 10 entries starting from the first item. For example, using HTTP GET against https://usX.api.mailchimp.com/3.0/lists will only get the first 10 lists. In order to get more than 10 items or start from a particular item, count and offset parameters need to be applied when calling HTTP GET.
For example, in order to get more than 10 lists (e.g. get 500 lists at once), append the count=500 to the uri like this:
A real world scenario to work with pagination is that, previously at some point, MailChimp API 3.0 couldn't handle HTTP GET request that gets more than 1000 list members at one go (If there are thousands of members within a list, calling HTTP GET to that list would result in HTTP 500 Internal Server Error from MailChimp server). Therefore all list members had to be retrieved by multiple batches, where count and offset parameters were used to solve this problem.