Loading...

Bind a list that stays in sync

The feed keeps a file current; a list bound to that file is the searchable mirror of your system.

Create a list and bind it

Create a list — catalog — and attach an embedding model if you want search by meaning (your manifest marked description as vectorised). Then bind it to the feed's file with keep in sync on and create fields on, so the roles your manifest declared are set up for you.

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

{ "account_name": "Demo", "list_name": "catalog", "subscription_name": "Basic", "model_name": "google-gemini-embedding-2" }
POST https://api.searchstack.dev/search-result/Demo/catalog/import-from-media
X-API-Key: {your key}
Content-Type: application/json

{ "store_name": "default", "file_path": "feeds/catalog-api.sync", "keep_in_sync": true, "create_fields": true }

Deletes propagate too

Because your endpoint declares itself a complete snapshot, Search Stack does a set difference on each sync. The full lifecycle flows from that one endpoint:

  • New row — appears as a new record.
  • Edited row — updates in place, matched by its id.
  • Removed row — any record in the list but no longer in your feed is deactivated on the next sync, with nothing for you to do.

Go deeper: Binding a list, keep-in-sync, and snapshot deletion in the reference.

Top