Content API sunsets August 18: seven Merchant API migration controls.

Fixed source-code dependency review

USD 249 fixed opening sample. Target: three business days after the private scope is accepted.

Included. One authorized source archive or repository snapshot; up to 25 observed legacy call sites, three scheduled jobs and three Merchant sub-APIs; a completed method inventory, ranked migration risks, source cutover checklist and one review round.

Delivery pass. Every observed call site is marked mapped, retired or explicitly unresolved, with its evidence gap and next cutover action recorded.

Not included. Live account access, credentials, API calls, developer registration, data-source creation, catalog upload, production cutover or support SLA. Scope beyond 25 call sites, three jobs or three sub-APIs is returned as a separate scope; it is not added or charged automatically.

Check fit without sharing code. This is a public GitHub form, so your GitHub username is visible. It does not request a company or repository name, code, credentials, Merchant IDs, feeds, private URLs or customer data, and it is not an order or payment request.

Seven controls before the Content API shutdown

1. Inventory legacy exposure and ownershipList every call site, scheduled job, runtime or library, response dependency and owner, then verify zero unexplained legacy traffic.
2. Register the developer and limit authorityEvidence the production project registration, API Developer contact, authentication type and required roles without retaining account IDs or credentials.
3. Map every method and sub-API contractRecord exact Merchant API v1 request, response, error and status semantics—not only a hostname swap.
4. Preserve identity and data-source ownershipStore full resource names, backfill dataSource names, keep offerId continuity and test reserved-character encoding.
5. Transform payloads and money deliberatelyMap productAttributes, amountMicros, currencyCode, update masks and future enums with exact fixtures.
6. Make pagination, concurrency and quota observableReplace customBatch, consume every page token, retain item-level outcomes and test quota budgeting plus bounded 429 retries.
7. Reconcile processed state and stage the cutoverInspect Product.productStatus, destinationStatuses and itemLevelIssues, canary one small segment and define rollback thresholds.

Keep one method inventory and one synthetic proof set

Start locally with the credential-free scanner. The open-source lineageproof merchant-scan command inventories supported source files for legacy endpoints, client libraries, Apps Script services, methods, productstatuses and customBatch. It makes no network request and writes no source snippets, credentials, Merchant IDs or API responses.

Download the deterministic Python scanner, then run python3 merchant-api-legacy-scan.pyz merchant-scan --source /path/to/authorized-source --out merchant-scan-output. It requires Python 3.11 or newer, installs no package and can be inspected as a standard ZIP archive. Its SHA-256 is 556affee3266bc605d8b4ffdbb07b3b18bc71f843be33bae38dd7c26cfeb1328; the deterministic build script is public.

Inspect the synthetic JSON inventory or synthetic CSV inventory, then review the scanner source. Static findings identify review candidates; they do not prove runtime coverage, a live account state or a completed migration.

Download the blank method inventory, compare it with the single-row transformation example, then inspect the five-call-site synthetic audit receipt for mapped, retired and unresolved dispositions.

Download the two-page migration readiness checklist (PDF) for the same seven pass/fail controls, synthetic disposition receipt and fixed review boundary.

• Every observed legacy call maps to a reviewed Merchant API method or an explicit retirement decision.
• Developer registration and authentication are evidenced without retaining credentials or account identifiers.
• Identifier tests cover REST resource names, feed labels, offerId continuity and reserved-character encoding.
• Every product-input write names the intended data source and verifies the processed Product separately.
• Price fixtures prove micros conversion without floating-point drift.
• Pagination and concurrent execution retain item-level outcomes, quota counts and bounded retry evidence.

Google Ads Scripts need a dependency cutover too

Google now lists Merchant API sub-APIs as individually enabled Advanced APIs for Google Ads Scripts. That makes the script creator and authorizing user part of the migration evidence: only the creator can change its Advanced API dependencies, calls use the authorizing user's permissions, and a new user can be prompted to configure those dependencies again if the creator is later removed from the account.

A source scan should therefore include the ShoppingContent advanced service, the enabled Merchant sub-APIs, the dependency owner and the authorizing user's required Merchant Center access. A correct method rewrite is not a cutover if the replacement service is unavailable to the running script.

Review Google's current Advanced APIs guidance.

Review source and synthetic fixtures first

• No password, OAuth token, service-account JSON, session cookie or payment information.
• No Merchant Center account ID, real product feed, customer record or proprietary source in a public inquiry.
• No production write, account configuration change, data-source creation or live cutover.
• No claim of Google affiliation, Google endorsement, complete migration or production performance.