{"title":"Feeds","slug":"feeds","url":"https://support.storeconnect.com/articles/feeds","url_markdown":"https://support.storeconnect.com/articles/feeds.md","subtitle":null,"summary":"Publish a chosen set of store records at a public URL in JSON, XML, CSV or another format, defined by a query and a Liquid template rather than by code. Use this section to build a catalog or data feed another system fetches.","type":"Developer_Documentation","video_url":"","keywords":"feeds, feed endpoints, data feed, product feed, catalog feed, json feed, xml feed, csv feed, marketplace feed, query, machine readable, integration","last_modified":"2026-10-20T05:28:05+0000","body_markdown":"A feed publishes a set of records from your store at a public URL, in a format another system can read. A supplier fetches `https://shop.example.com/feeds/products.csv` each night to see your current catalog and prices. A marketplace reads the same records as XML. A partner's script reads them as JSON.\n\nYou decide what a feed contains and what it looks like. A **Query** record picks the records, from any object StoreConnect syncs to the storefront. A **Feed** record carries a Liquid template that renders them, in JSON, JSON Lines, XML, CSV, HTML, Markdown or plain text. A **Store Feed** record mounts the result at a path in one store. Nothing is deployed and no endpoint is written: a feed is three saved records.\n\nA feed is public and unauthenticated. Anyone with the URL can read it.\n\nFeeds are not the [StoreConnect API](storeconnect-api), which is authenticated, reads and writes, and exposes endpoints StoreConnect defines. A feed is read-only output that you define yourself. Feeds are also separate from the [Google Merchant feed](google-merchant-feed) and the [Facebook catalog data feed](facebook-catalogue-data-feed), which StoreConnect generates automatically on fixed paths and you cannot change.\n\n## When to use a feed\n\nA feed fits when another system needs your data on a repeating basis and on its own terms. You shape the output to the format that system already expects, and it either reads the URL or receives a push on a schedule, so neither side has to build anything to translate between you.\n\nIt also serves as a straightforward extract when someone just needs the data once. The URL opens in a browser or a spreadsheet, and the HTML, Markdown and plain-text formats are there for output a person reads rather than a program.\n\nBecause a feed is public, the question to settle first is not what you want to publish but what you would accept anyone reading. Catalog and content data suit a feed. Customer, order and payment data do not belong in one.\n\n## In this section\n\n- [Set up a feed](set-up-a-feed) — create the three records, choose the formats, and decide whether the feed renders on request or is built to a schedule and delivered\n- [Feed query language](feed-query-language) — the clauses that decide which records a feed contains\n\nFor the field-level definitions of the records involved, see [Feed object reference](feed-object-reference), [Query object reference](query-object-reference) and [Store Feed object reference](store-feed-object-reference)."}