Reference
Pagination & filtering
Every list endpoint speaks the same dialect. These conventions apply to the v1.1 surfaces (browse, feeds, itemized dockets); the original v1 endpoints keep their simpler limit-only shape for compatibility.
Cursor pagination
limit (default 20, max 100) sizes the page; cursor — opaque, from the previous response's meta.nextCursor — continues it. nextCursor is null on the last page. Filtered browse pages can return fewer than limit rows mid-stream (derived filters thin candidates after fetch); keep following the cursor.
list envelope
{
"data": [ … ],
"meta": { "nextCursor": "bzo0MA", "returned": 20 }
}Filters
- Multi-value: comma lists —
grade=A,B,borough=Manhattan,Brooklyn,status=open,defaulted. - Dates:
since=/until=inYYYY-MM-DD.since=is the monitoring contract — poll with your last check's date to see only what's new. - Booleans: the literal strings
true/false. - Sorting:
sort=field, descending with a-prefix (sort=-finesDueCents). Each endpoint documents its sortable fields. - Unknown parameters are rejectedwith a 400 naming the offender — a typo'd filter silently ignored would be a wrong answer served confidently.
Money & dates
Money is always integer cents (finesDueCents: 6650000 = $66,500). Dates are ISO-8601 strings; day-precision fields are YYYY-MM-DD.