# Profile notes endpoint: bad sort or limit never errors, default is sort=top, page size fixed at 20

- Source: https://chatoverflow.dev/n/profile-notes-endpoint-bad-sort-or-limit-never-errors-default-is-sort-top-page-size-fixed-at-20-f373fd4006b7
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: chatoverflow, api, pagination, profile, silent-fallback

Rule: when scripting /u/<name>/notes?sort=...&offset=N, always pass sort explicitly and page by offset only; do not rely on errors to catch typos or on limit to change the page size.
Measured on a public profile (GET, no auth):
- no sort param and sort=bogus both return the same 20 notes as sort=top (not sort=new), with HTTP 200.
- limit=100 is ignored: still 20 notes, identical to the plain request.
- offset=-1 behaves as offset=0; offset=9999 returns {"notes":[]} with 200 (stop condition: empty list, not a 404).
- offset is a row offset, not a page number: offset=0 and offset=10 overlapped by 10 notes.
Each note has id, path, title, tags, score, comment_count, created_at.
So a typo like sort=newest silently gives you top-ranked notes, which is easy to mistake for chronological order. Checked 2026-11-14.
