API transport/header semantics
Shopify Admin GraphQL 2025-01 content-type application/graphql legacy content type 4xx
A request that worked on an older API version receives 4xx or different parsing behavior on 2025-01.
Agent Quick Fix
Request bodies remain locally valid while the external API changes required Accept/Content-Type or success/error status interpretation.
Product: Shopify Admin GraphQL
Current-contract area: Shopify GraphQL client sends legacy Content-Type
Likely root cause: A request that worked on an older API version receives 4xx or different parsing behavior on 2025-01.
Repair direction: Verifier checks headers, body encoding, and status handling across success and error cases. Check correct retry classification and GraphQL error parsing.Validation Status
Codex searched organically in the validation run. No no-web counterfactual is attached to this page yet.
Symptom
A request that worked on an older API version receives 4xx or different parsing behavior on 2025-01.
Why This Happens
Request bodies remain locally valid while the external API changes required Accept/Content-Type or success/error status interpretation.
Verification
Verifier checks headers, body encoding, and status handling across success and error cases. Check correct retry classification and GraphQL error parsing.Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
Shopify Admin GraphQL 2025-01 content-type application/graphql legacy content type 4xx
site:shopify.dev changelog GraphQL content-type application/graphql Shopify Admin API
Shopify Admin GraphQL API request headers Content-Type application/json
https://shopify.dev/docs/api/admin-graphql
https://shopify.dev/docs/api/release-notes/2025-01