Use case
Feedvault for product catalogues
Most small shops keep their catalogue in a spreadsheet or export it from their shop system as CSV. Feedvault turns that file into a search API your website, a mobile app or a partner can query, without building or hosting a backend.
When a catalogue API helps
- Your website needs live product data (price, stock, category) from a list you maintain in a spreadsheet.
- A partner or reseller wants your catalogue in a machine-readable way, with their own access you can revoke.
- You are building a prototype or an internal tool and do not want to write and host CRUD code first.
If you already run a full e-commerce platform with its own API, use that. Feedvault is for data you own that lives in files.
Prepare the CSV
- One row per product, one column per field: sku, name, price, currency, category, stock, updated.
- A unique key column, usually the SKU. Re-imports use it to update rows instead of duplicating them.
- Plain numbers in number columns. Feedvault normalises common formats (for example "AED 52.50" to 52.5), but consistent data is easier to query.
- Dates in one format, ideally ISO (2026-11-16).
Preview the file first with the free CSV to JSON converter. It shows the columns and types Feedvault will infer, entirely in your browser.
Import and review the schema
Create a dataset, add a provenance note (for example "Product export from our shop system, maintained by the operations team") and upload the CSV. Feedvault infers each column's type and normalises values. Review the schema: mark the SKU as the key, mark name and category as searchable, and set which columns are required. Large files import in slices in the background.
Create keys for each consumer
Create an API key for your website and a separate one for each partner. Each key has its own rate limit and can have its own monthly quota and alert threshold, and you can revoke a key without affecting the others. The secret is shown once; store it like a password, server side.
Query the catalogue
Requests go to the dataset's records endpoint with the key in the Authorization header. Filters use the form filter[column][operator]=value; sort with sort=column or sort=-column for descending.
| Question | Query |
|---|---|
| Kitchen products under 60 | filter[category][ieq]=kitchen & filter[price][lt]=60 |
| In stock, cheapest first | filter[stock][gt]=0 & sort=price |
| These three SKUs | filter[sku][in]=MUG-12,MUG-14,BOWL-3 |
| Name contains "linen" | filter[name][icontains]=linen |
Operators include eq, ne, lt, lte, gt, gte, in, nin, case-insensitive ieq, icontains and ilike, and null checks; which ones are allowed depends on the column type.
Keep it up to date
When prices or stock change, export the CSV again and import it into the same dataset. Rows are matched by the key: existing products are updated, new ones added, and Feedvault records what changed. A record that is no longer in the file is not deleted automatically, so mark discontinued products in a column (for example active = false) and filter on it.
Watch usage
Feedvault meters requests per key per month and shows usage in the app, with alerts as a key approaches its quota. Alerts appear in the app; email alerts and outbound webhooks are not available yet.
Questions and answers
Can the website call Feedvault directly from the browser?
Keep API keys on a server. Call Feedvault from your backend or a serverless function and pass the results to the page.
Does Feedvault sync with my shop automatically?
No. It imports files you upload. Re-import a fresh export whenever the data changes.
How big can a catalogue be?
Imports run in slices, so thousands of rows work; the monthly import allowance depends on your plan.