Search and feeds as public read endpoints
Anonymous search is published-only and offset-addressed; a feed’s `/rss` and `/items` force published-plus-site onto whatever query the feed stores.
Two families of read endpoint answer without credentials, and both of them are narrower than they look: search is public only while you ask for published rows, and of a feed's three read routes only two are safe to expose.
Search
/api/v1/search?q=&siteId=&status=publishedNo authPublic with status=published. Omit status, or
name any other one, and the request needs a bearer token and access to the site —
an omitted filter could return drafts, so it is treated as a request for them rather than
as a convenience.
{
"data": [
{
"id": "4f2a…",
"title": "Pricing",
"slug": "pricing",
"contentTypeName": "page",
"status": "published",
"summary": "What each plan includes.",
"publishedAt": "2026-08-14T09:12:00.000Z"
}
],
"meta": { "total": 12, "page": 1, "pageSize": 20, "totalPages": 1, "hasMore": false }
}Search parameters
The limit clamp is load-bearing, not tidiness: each matching
row is read with its body and layout so an empty summary can fall back to the page's real
copy, so an uncapped ?limit= would turn one anonymous request into an
arbitrarily large read. Paging is by offset, and meta.hasMore is
computed from the offset you actually sent rather than from page arithmetic — a
non-aligned offset would otherwise be reported as having more rows left than it does.
| Name | Type | Default | Description |
|---|---|---|---|
qrequired | string | — | Absent or empty is a 400. Only whitespace-only reaches the query itself, where it is zero results. |
siteIdrequired | string | — | Config slug or DB UUID. |
status | string | — |
|
contentType | string | — | One content type name. |
locale | string | — | Exact match on the row’s locale. |
limit | integer | 20 | Clamped to 1–100. |
offset | integer | 0 | Rows to skip. Negative values clamp to 0. |
The query text goes to Postgres through websearch_to_tsquery, which takes arbitrary input by contract: a colon, an ampersand, a stray bracket or an unpaired quote are tokens, not syntax errors. Multiple words are ANDed, a quoted phrase matches adjacency, or becomes alternation and a leading - negates; input that reduces to nothing matches nothing. Matching runs over the title, body and summary and the page's layout copy, so a page composed entirely of modules is findable on its own words, and results come back ranked by relevance with no secondary ordering.
{ "error": { "code": "BAD_REQUEST", "message": "Query parameter \"q\" is required" } }Feeds
A saved feed is a stored query. Three routes read one, and they differ in whether they trust what was stored.
/api/v1/feeds/:slug/itemsNo authRuns the feed's query with status: 'published' and the resolved
site forced over whatever the feed itself was configured with, then answers in the standard
{ data, meta } list envelope. Page-addressed.
/api/v1/feeds/:slug/rssNo authThe same forced query, rendered as RSS 2.0 with an
application/rss+xml content type.