[DOC] Please add documentation on how to request other pages in a paginated response.

[Guus der Kinderen]

While trying to figure out how to get all attendees for a particular event, I stumbled upon paginated responses. 

The concept of Eventbrite pagination is explained here: https://www.eventbrite.com/developer/v3/reference/pagination/ However, I didn't find documentation on how to "scroll" through paginated result sets. 

Given the remark (found on the pagination documentation page) that page sizes are set, I guestimated that only a page-number is required in the request, and page size need not be provided. Using the parameter "page_number" (as found in API responses) as a query parameter causes an error, but I later found that simply using "page" works. Example: https://www.eventbriteapi.com/v3/events/EVENTID/attendees/?page=2

It would be helpful if the documentation makes mention of this. If it's already in there somewhere, it clearly lacks the <blink>, <em> and <h1> tags ;)

[Carlos Mostek]

I second this request.  I've been hunting all evening trying to figure out how to set this.  Thank you Guus for figuring this out.  I tried page_number, pagination.page_number, page_id, etc.  Didn't try page by itself, that does seem to work!

[Malina Wiesen]

Hi Carlos,

Thanks for the feedback. I agree, we can do a better job of documenting pagination. As the previous poster indicated, passing in a "page=X" parameter on the query string will return the page you send as X.

[rainer...@gmail.com]

This does not work for me. Whatever page number I provide, I get always the first 50 items. Following queries yield identical results:

/v3/events/:id/attendees/?page=1
/v3/events/:id/attendees/?page=2
/v3/events/:id/attendees/?page=2&last_item_seen=<lrgest id from page 1>

Any ideas how get page 2?

[rainer...@gmail.com]

Solve: my fault, the actual URL in the request had a '/' appended