feat: add limit/pagination to events endpoint #147

New Issue

cal · 2026-03-24T03:40:07Z

cal commented

2026-03-24 03:40:07 +00:00

The GET /api/v2/events endpoint returns all records with no limit parameter. Add an optional limit: int query param (default 100, max 500).

Found during smoke test development — endpoints without limits cause excessive data transfer.

The `GET /api/v2/events` endpoint returns all records with no `limit` parameter. Add an optional `limit: int` query param (default 100, max 500). Found during smoke test development — endpoints without limits cause excessive data transfer.

Claude added the

ai-working

label 2026-03-24 06:31:07 +00:00

cal referenced this issue from a commit

2026-03-24 06:32:24 +00:00

feat: add limit/pagination to events endpoint (#147)

Claude referenced a pull request that will close this issue

2026-03-24 06:32:30 +00:00

feat: add limit/pagination to events endpoint (#147) #156

Claude added the

ai-pr-opened

label 2026-03-24 06:32:37 +00:00

Claude commented

2026-03-24 06:32:38 +00:00

PR opened: #156

Added limit: Optional[int] = 100 to GET /api/v2/events, capped at 500 via max(0, min(limit, 500)). Applied after all filters, before CSV/JSON branch — same pattern as the other 5 paginated endpoints.

PR opened: https://git.manticorum.com/cal/paper-dynasty-database/pulls/156 Added `limit: Optional[int] = 100` to `GET /api/v2/events`, capped at 500 via `max(0, min(limit, 500))`. Applied after all filters, before CSV/JSON branch — same pattern as the other 5 paginated endpoints.

Claude removed the

ai-working

label 2026-03-24 06:32:41 +00:00

cal closed this issue

2026-03-24 12:09:47 +00:00

cal referenced this issue from a commit

2026-03-24 12:09:47 +00:00

Merge pull request 'feat: add limit/pagination to events endpoint (#147)' (#156) from issue/147-feat-add-limit-pagination-to-events-endpoint into main

Sign in to join this conversation.