What is this site not?
It is not Meta’s API Upgrade Tool, not a hosted scanner of your app traffic, not legal advice, and not a guarantee that your integration will survive cutover. It is a local decision checklist with copyable search strings so humans can inspect code and workflows before 27 October 2026.
How is this different from the API Upgrade Tool?
The Upgrade Tool highlights calls Meta already sees in your app’s traffic. This matrix helps when you need an offline inventory: pinned-version false safety, strings that may live only in automation nodes, and commerce endpoints that need a business decision rather than a field rename. Use both if you can.
What changes about batching after root /?ids= dies?
Meta suggests per-object requests or batch POSTs. A batch returns a list of per-call responses instead of a single map keyed by ID, and each batched call still counts toward rate limits. Plan both the request assembly and the response parser, not only the URL change.
Is anything uploaded from this page?
No. Radio selections and generated checklists stay in your browser. There is no account system and no server endpoint that receives your answers. Hosting may still see ordinary CDN request metadata for page loads.
What if commerce_orders is in our code?
Treat it as a hard stop: Meta documents removal without a replacement API when remaining versions lose Commerce Order Management on 27 October 2026. Escalate to whoever owns Facebook/Instagram checkout order operations; do not expect a drop-in Graph rename.