<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pagination on API Course</title>
    <link>https://apicourse.com/tags/pagination/</link>
    <description>Recent content in Pagination on API Course</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicourse.com/tags/pagination/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>API Pagination: Offset, Cursor, and Keyset Patterns</title>
      <link>https://apicourse.com/api-pagination-offset-cursor-and-keyset-patterns/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/api-pagination-offset-cursor-and-keyset-patterns/</guid>
      <description>&lt;p&gt;Returning a list of items from an API sounds simple until the list has ten thousand items. At that point, the response is too large to transfer efficiently, too slow to serialize, and too expensive to compute. Pagination is how APIs break large result sets into manageable chunks that clients can fetch incrementally. Choosing the wrong pagination pattern — or implementing the right one incorrectly — creates problems that do not appear until production load reveals them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
