Fetch API
Fetch a Listing
POST
Fetch a Search Listing — a searchable, filterable, sortable, paginated collection. The body controls every aspect of the query: parameters that scope the listing (e.g. a category ID), free-text
search, structured filter expressions, sort, and pagination via page + limit.
Path Parameters
Your project’s Fetch token, embedded in the subdomain.
The listing’s slug, e.g.
<listing-slug>. Per project — see your listing’s detail view in the API Builder.Headers
See Headers on the overview for the full set. Listings honourfs-context, fs-domain, fs-version, and fs-secret (only when the project has fetch keys configured).
Request Body
All body fields are optional unless the listing’s parameter definition declares one as required. Only six top-level keys are accepted; any other key returns400 Bad Request.
Listing parameters. Shape is defined per listing in the API Builder. Required keys must be present; values are typed (string or array of strings).
Structured filter expressions. Each entry is one of three shapes:For
equals / contains
range
or / not (nested)
range, supply from, to, or both. Filter field values must be among the listing’s configured filter fields.Sort instructions. Accepts three shapes:
field name (defaults to asc)
sort object
array of sort objects (applied left-to-right)
order is "asc" or "desc". field values must be among the listing’s configured sort fields.Free-text search query. Must be non-empty after trim. Searches across the listing’s configured search fields.
Page number (1-based).
Items per page. Capped by the listing’s configured
perPageMax.Response
Returns the listing’s records as defined by the per-item block, plus pagination metadata. Exact shape depends on the listing definition — generate the Client SDK for typed access.Status codes
| Code | When |
|---|---|
200 | Listing rendered (may have zero items) |
400 | Body validation failed — unknown filter field, sort field not in allowed sorts, limit above the configured max, search empty, etc. The details array spells out each violation. |
401 | fs-secret missing or wrong (only when the project has fetch keys configured) |
404 | Listing slug doesn’t exist for the resolved context |
403 | Project’s plan limit for Fetch API requests exceeded |