Content API vs feed file

Content API vs feed file: the comparison

Rows below draw on Google's 'How to upload your products to Merchant Center' help page, the Merchant API overview and the Merchant API 'Migrate data sources' guide, fetched on the date in the footnote. Where a page does not state a fact, the cell says so.

What changed with the Content API sunset

Google's Merchant API overview states it plainly: the Merchant API is a redesign of the Content API for Shopping, and Content API for Shopping was sunset on August 18, 2026, with requests experiencing progressive errors from September 1, 2026. Teams that need more time can apply for extended access. The Merchant API is described as enabling automation of account, product and inventory management within Merchant Center, and as complementing other product data upload methods like files and autofeed.

For data sources specifically, the migration guide lists the practical differences. Identifiers change from a numeric datafeedId to a string name; datafeed methods map to dataSources methods; file upload status moves to a read-only fileUploads resource, fetched with the 'latest' alias, with errors and warnings merged into a single issues list with severities. Batch operations for datafeeds are gone, updates use PATCH instead of PUT, multi-target feeds are deprecated so each data source has a single target, the fetch method only works for file-input sources, and data source rule migrations must be done by hand in the Merchant Center UI. Most importantly for anyone comparing API and file: you must explicitly create data sources before uploading products, whereas the Content API created a 'Content API' data source automatically.

What a feed file gives you

Google's upload guide describes the file path as a file containing all product details, each mapped to Google's attribute list, which can combine data from several sources. You can upload it once from your computer or host it at a URL that Merchant Center syncs every 24 hours, and you can still upload a new file at any time. A Google Sheets template follows the same 24-hour sync. The file can be up to 4 GB. The guide's warning applies to both paths: incorrectly formatted or missing data causes errors in the account.

A file is inspectable. You can open it, count rows, diff two versions and hand it to a colleague without credentials. It is also whole: Google's RSS guidance says removing a product from the file removes it from Merchant Center, so a feed file is always the complete catalog, never a delta. The cost is latency: with a 24-hour fetch, a price change at 09:00 may not show until the next fetch, unless you trigger a fetch or upload manually.

What the API gives you

Google says the Merchant API lets apps interact directly with Merchant Center to manage configuration, act as a product data input source and provide reporting, and strongly recommends it for large numbers of feeds or frequent product data changes. A successful API response means Merchant Center accepted the data for processing, not that the product is approved to show. In Merchant API, a product insert needs a data source of API input type created first, and account-level settings such as autofeed can be toggled through autofeedSettings.

The API is for systems, not people. You need OAuth or service-account credentials, quota handling, retry logic and a migration every time Google redesigns the surface, as it just did. Third-party write-ups describe feeds as refreshing once or twice daily and the API as allowing updates within minutes; Google's own pages give the 24-hour file fetch and the 'frequent changes' recommendation, so treat the minutes figure as a vendor claim rather than a Google one.

Where a feed tool sits

Textfinity takes the file path. It reads the store (Shopify natively, or a CSV, Google Shopping XML or Google Sheet URL), applies mapping and filter rules, and publishes a complete comma-delimited CSV (or TSV) on a stable URL. We register that URL in Merchant Center with you as a scheduled-fetch file source (you give us access, or we walk you through it), a one-time step. Google then fetches the file on its schedule; Merchant Center takes the comma CSV in production, even though Google's help lists .txt, .tsv and .xml by extension. Feeds rebuild on a per-shop schedule and within about five minutes of an edit; median rebuild is 10.9 seconds.

What Textfinity does not do: push individual products through the products API, or read back product statuses or disapprovals. If your catalog needs sub-daily price or stock updates in Merchant Center, you need API tooling on the products side, and the honest recommendation is a developer integration or a platform with a products-API connector. For everyone whose data changes daily or slower, the file path is simpler to run and far easier to debug. Clients who want programmatic access to their own setup can connect an AI assistant to Textfinity over MCP to search products, read a feed's output and edit mapping or filter rules; that is a way to manage the feed, not a products API.

Changes daily or slower, want to inspect the file     -> hosted feed file (Textfinity builds it)
Many feeds, frequent intra-day changes, dev team      -> Merchant API products upload
Platform connection already syncing                    -> keep it; add a feed file for other channels
Content API integration still running                  -> migrate: sunset 2026-08-18, errors from 2026-09-01