Paging with limit and offset in Endpoints using a personal api-key is not allowed
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
Bug Description
When using paging in Endpoints by specifying limit and offset while using a personal api-key ( e.g. using curl ) we receive the following error:
OFFSET is not supported on queries made with a personal API key. For pagination, use keyset pagination on the timestamp column, e.g. WHERE timestamp > :last_seen_timestamp ORDER BY timestamp LIMIT N. For bulk data extraction, use batch exports: https://posthog.com/docs/cdp/batch-exports\",\"attr\":null}
Debug info
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report with curl against the affected Endpoints request, using a personal API key with both limit and offset. Trace the pagination and API-key handling involved, then confirm the intended behavior and add coverage showing the accepted pagination behavior or a clear validation response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100