09-advanced-querying

Add validated pagination, sorting, and filtering to collection endpoints.

Updated Mar 9, 2026

Search Tags:#security #scalability #api #backend #filter #sort #paginate

Ready to run

npx skills add https://github.com/kennypallchizaca-coder/agentic-full-stack-skills --skill 09-advanced-querying

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: 09-advanced-querying
Source: https://github.com/kennypallchizaca-coder/agentic-full-stack-skills/tree/main/skills-backend/09-advanced-querying
Command: npx skills add https://github.com/kennypallchizaca-coder/agentic-full-stack-skills --skill 09-advanced-querying

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

List endpoints often fetch unbounded data, risking performance and resource exhaustion. This skill introduces validated query parameters, bounded pagination, sortable fields, and stable metadata to keep APIs scalable and predictable.

Core Features & Use Cases

Validated query parameters for page, limit, sort, and filters.
Bounded pagination with max page size to prevent abuse.
Allowlisted sort/filter fields and server-side enforcement.
Consistent response metadata including total, page, and limit.

Quick Start

Configure a collection endpoint to accept page, limit, sort, and filter parameters with safe defaults and return data alongside metadata.

Frequently Asked Questions about 09-advanced-querying

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

FAQPage Schema

How do I implement safe pagination and filtering for API list endpoints?▼

Safe pagination and filtering for API list endpoints is implemented by enforcing input validation, applying page size caps, and using allowlisted fields for sort and filter operations. This ensures predictable data retrieval and prevents resource exhaustion.

Why does my backend list endpoint return unbounded data and how do I fix it?▼

Unbounded data fetching in backend list endpoints occurs when query parameters lack validation and limits. Fix it by applying bounded pagination with maximum page size constraints, validated query inputs, and allowlisted sort and filter fields to prevent performance issues.

What is the best way to secure collection endpoint queries against abusive requests?▼

Securing collection endpoint queries requires enforcing bounded pagination with maximum page size caps, validating all query parameters, and restricting sorting and filtering to server-side allowlisted fields to constrain the dataset and prevent abuse.

How do I add sorting and searching constraints to a constrained dataset API?▼

Adding sorting and searching constraints to a constrained dataset API involves translating validated query parameters into repository-level queries using an allowlist of permitted fields, ensuring only authorized columns are accessed during data retrieval.

Can I use server-side allowlisted fields to prevent unsafe query parameters in my API?▼

Yes, server-side allowlisted fields can be used to prevent unsafe query parameters by validating inputs against a predefined list of permitted sortable and filterable columns before translating them into repository-level queries.

What limitations exist when applying bounded pagination to API collection endpoints?▼

Bounded pagination limitations include enforcing a maximum page size cap to prevent abuse, requiring input validation for all query parameters, and restricting sorting and filtering strictly to allowlisted fields within the constrained dataset.