Why Pagination with limit and offset in Rest API? - Purpose & Use Cases

The Big Idea

What if you could load only what you need, making your app lightning fast and easy to use?

The Scenario

Imagine you have a huge list of items, like thousands of products in an online store, and you want to show only a few at a time on a webpage.

Without pagination, you might try to load all items at once, which can be overwhelming and slow.

The Problem

Loading all items at once makes the page slow and hard to use.

It also wastes data and memory, especially on slow internet or small devices.

Manually slicing the list each time is repetitive and error-prone.

The Solution

Pagination with limit and offset lets you ask for just a small chunk of items at a time.

Limit tells how many items to get, offset tells where to start.

This way, you load only what you need, making apps faster and easier to use.

Before vs After

✗ Before

all_items = get_all_items()
page_items = all_items[start:end]

✓ After

page_items = get_items(limit=10, offset=20)

What It Enables

It enables smooth browsing through large lists without waiting or crashing.

Real Life Example

When you scroll through search results or product pages, pagination loads just a few results per page, making the experience quick and responsive.

Key Takeaways

Loading all data at once is slow and inefficient.

Limit and offset let you fetch small parts of data step-by-step.

This improves speed, user experience, and resource use.

Practice

1.

What does the limit parameter control in pagination?

easy

A. The starting position of items to return

B. The sorting order of the items

C. The total number of items in the database

D. The number of items to return in one page

Solution

1. Step 1: Understand the role of limit

   The limit parameter sets how many items you want to get back in one page of results.

2. Step 2: Differentiate from offset

   The offset controls where to start, not how many items to return.

3. Final Answer:

   The number of items to return in one page -> Option D

4. Quick Check:

   limit = number of items per page [OK]

Hint: Limit sets count of items per page, offset sets start point [OK]

Common Mistakes:

• Confusing limit with offset
• Thinking limit controls sorting
• Assuming limit is total items

2.

Which of the following is the correct way to request the second page of results with 10 items per page using limit and offset?

GET /items?limit=10&offset=?

easy

A. 10

B. 20

C. 0

D. 1

Solution

1. Step 1: Calculate offset for second page

   For page 1, offset is 0. For page 2, offset = limit * (page_number - 1) = 10 * (2 - 1) = 10.

2. Step 2: Confirm limit remains 10

   Limit stays 10 to get 10 items per page.

3. Final Answer:

   10 -> Option A

4. Quick Check:

   offset = limit * (page - 1) = 10 [OK]

Hint: Offset = limit x (page number - 1) [OK]

Common Mistakes:

• Using offset = page number
• Using offset = limit x page number
• Setting offset to 0 for second page

3.

Given the following API call, what items will be returned if the full list is ["a", "b", "c", "d", "e", "f"]?

GET /items?limit=2&offset=3

medium

A. ["d", "e"]

B. ["c", "d"]

C. ["a", "b"]

D. ["e", "f"]

Solution

1. Step 1: Understand offset and limit

   Offset 3 means start from the 4th item (0-based index), which is "d".

2. Step 2: Select 2 items from offset

   Limit 2 means take 2 items starting at "d", so items are "d" and "e".

3. Final Answer:

   ["d", "e"] -> Option A

4. Quick Check:

   Start at index 3, take 2 items = ["d", "e"] [OK]

Hint: Offset is start index, limit is count from there [OK]

Common Mistakes:

• Starting count at 1 instead of 0
• Taking wrong slice of items
• Confusing offset and limit roles

4.

Identify the error in this API call for pagination: GET /items?limit=5&offset=-10

medium

A. Offset should be a string

B. Limit cannot be 5

C. Negative offset is invalid

D. Limit must be greater than offset

Solution

1. Step 1: Check offset value

   Offset represents the starting position and cannot be negative because you cannot start before the first item.

2. Step 2: Validate limit and offset rules

   Limit can be any positive number; offset must be zero or positive.

3. Final Answer:

   Negative offset is invalid -> Option C

4. Quick Check:

   Offset ≥ 0 required [OK]

Hint: Offset must never be negative [OK]

Common Mistakes:

• Allowing negative offset
• Confusing limit and offset roles
• Assuming offset can be string

5.

You have 53 items and want to paginate with limit=10. How many pages will you have, and what is the offset for the last page?

hard

A. 5 pages, offset 40

B. 6 pages, offset 50

C. 6 pages, offset 45

D. 7 pages, offset 60

Solution

1. Step 1: Calculate total pages

   Total pages = ceiling of total items / limit = ceil(53 / 10) = 6 pages.

2. Step 2: Calculate offset for last page

   Offset for last page = limit x (pages - 1) = 10 x (6 - 1) = 50.

3. Final Answer:

   6 pages, offset 50 -> Option B

4. Quick Check:

   Pages = 6, offset last = 50 [OK]

Hint: Pages = ceil(total/limit), offset = limit x (pages-1) [OK]

Common Mistakes:

• Using floor instead of ceiling for pages
• Calculating offset as limit x pages
• Ignoring leftover items on last page