Loading...
searchstack.dev
Sign In

Use it in your app

Your catalog list is a normal searchable list now — the fact that a feed keeps it fresh is invisible from here. You query it the same way you'd query any Search Stack list.

With the client library

@searchstack/public-api is a typed client for the whole search API, so you don't hand-write requests. Point it at your key and search the list: 

npm install @searchstack/public-api
import { SearchStackClient } from '@searchstack/public-api'

const client = new SearchStackClient({
  apiKey: 'YOUR_SEARCH_KEY',
  baseUrl: 'https://api.searchstack.dev',
})

const result = await client.Search.searchList('Demo', 'catalog', 1, {
  query: 'warm jacket for winter',
  filter: "brand eq 'Kestrel' and in_stock eq true",
  size: 10,
})

for (const hit of result.results) {
  render(hit.name, hit.fields)   // description, price, image_url…
}

Because the manifest marked description as vectorised, that query matches by meaning — "warm jacket for winter" finds the down jacket even though those words aren't in its text — and the brand/in_stock filter narrows it, all in one call.

Or plain HTTPS

The client is a convenience over ordinary requests, so any language works — it's a request to the same search endpoint:

POST https://api.searchstack.dev/search/Demo/catalog/1
X-API-Key: {your key}
Content-Type: application/json

{ "query": "warm jacket for winter", "filter": "brand eq 'Kestrel' and in_stock eq true", "size": 10 }

Wire that into a web page, a mobile app, a backend — wherever your search lives. And the same list is reachable over MCP, so an agent can search your synced data too, from the one key-scoped setup.

Go deeper: The search API — queries, filters and paging in the reference.

Top