Pagination
Page through large result sets with the x-page-offset and x-page-limit headers
Every GET endpoint in the Lemmy API is paginated. You control which slice of records you
receive using two required request headers, and the response tells you whether more
records are available.
Request headers
Both headers are required on every GET request. If you omit them, the request returns an
error. Always send x-page-offset and x-page-limit together.
Requesting a page
This requests the first 50 records, starting at offset 0:
Response headers
Each paginated response includes two headers that tell you whether to keep going:
To read an entire dataset, keep requesting pages — using x-page-next as your next
x-page-offset — until x-page-more reports that there are no more records.