How does pagination work in the WorkoutDB exercise API?
List endpoints return the page of results under data and the pagination context under meta — part of the standard { data, meta, requestId } envelope — so you page through search and filtered results with the same predictable shape on every call.
Paging through results
Search and filter calls return a page of exercises under data, with meta carrying the counts you need to render pagination — total results and the current window — so you can build "next/previous" or infinite scroll without guesswork. Because the envelope never changes, your pagination handling is written once.
Since the catalog is near-static and modest in size (~873 exercises), you can also cache pages by their query and filters, or pull broad slices and paginate client-side, to keep request counts low.
- Results under data, pagination context under meta.
- Same { data, meta, requestId } envelope on every list call.
- Combine with filters and a query; pagination applies to the filtered set.
- Cache pages by query/filters — exercise data rarely changes.
Related questions
- Where are total counts returned?
- Under meta in the response envelope, alongside the current page window, so you can render pagination controls accurately.
- Can I paginate filtered search results?
- Yes. Pagination applies to whatever query and combinable filters you pass, so you page through exactly the subset you asked for.
Build it on WorkoutDB
~873 exercises with demo video, ranked search, and four languages — over a clean REST API. Start free: 5,000 requests/month, no credit card.