pagination

Implement server-side and client-side API pagination strategies with pageToken and keyset filters.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/kineticdata/kinetic-platform-ai-skills --skill pagination-kineticdata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pagination
Source: https://github.com/kineticdata/kinetic-platform-ai-skills/tree/main/skills/platform/pagination
Command: npx skills add https://github.com/kineticdata/kinetic-platform-ai-skills --skill pagination-kineticdata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of efficiently retrieving large datasets from APIs that have record limits, preventing data loss and ensuring complete data access.

Core Features & Use Cases

  • Core API Pagination: Understand and implement pageToken for paginating results within the 1000-record cap.
  • Keyset Pagination: Learn how to bypass the 1000-record limit using createdAt filters for full data retrieval.
  • Task API Pagination: Utilize standard limit/offset for the Task API and its count field for lightweight queries.
  • Use Case: Retrieve all 5,000 submissions from a form that has a 1000-record API limit by implementing keyset pagination.

Quick Start

Use the pagination skill to retrieve all records from a form with more than 1000 submissions by implementing keyset pagination.

Frequently Asked Questions about pagination

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve more than 1000 records from an API with a page limit?

To retrieve more than 1000 records from an API with a page limit, implement keyset pagination using `createdAt` filters to bypass the cap and fetch the full dataset without data loss.

What is the difference between Core API pageToken and Task API limit/offset pagination?

Core API pagination uses a `pageToken` to navigate within the 1000-record cap, whereas Task API pagination utilizes standard `limit` and `offset` parameters alongside a `count` field for lightweight queries.

How do I implement keyset pagination to fetch all submissions from a large dataset?

Implement keyset pagination by applying `createdAt` filters to sequentially fetch records past the 1000-record API limit, ensuring complete data retrieval for large datasets like a 5000-submission form.

When should I use server-side aggregation instead of client-side pagination for dashboard KPIs?

Use server-side aggregation for dashboard KPIs and report metrics when you need to optimize data retrieval performance, bypassing the need to manually paginate large datasets client-side.