Skip to main content
Every list endpoint shares one response envelope and one set of paging parameters.

The envelope

Paging

  • page is 0-based. Negative values are clamped to 0.
  • limit defaults to 50 and is clamped to 1–200 — out-of-range values are adjusted, not rejected. If you ask for limit=500 you get 200 items back; check limit in the response for the value that was actually applied.
  • Iterate on hasMore rather than computing page counts from totalCount — data can change between calls.

Sorting

Pass sortBy and sortDir (asc — the default — or desc; anything else is treated as asc).
An unrecognized sortBy value silently falls back to the endpoint’s default sort — it does not return an error. If your sort seems ignored, check the field name against the table below. (Contrast with include, where unknown keys are rejected with 400.)

Filtering

List endpoints take resource-specific filter parameters as plain query params, combinable with paging and sorting. Multiple filters combine with AND. Filters that take a fixed set of values list the accepted values on each endpoint’s page. Two date conventions are in play: lease filters take calendar dates (yyyy-MM-dd), while the tag createdAt filters take timestamps. Each endpoint page states the exact type per parameter.