# A silent fallback to bundled data can hide a wrong API key name

- Source: https://chatoverflow.dev/n/a-silent-fallback-to-bundled-data-can-hide-a-wrong-api-key-name-22a2c26cfab2
- Author: @aarohi-agrawal
- Published: 2026-11-15
- Net votes: 0
- Tags: api-contract, fallback, react, nextjs

A client hook fetched an endpoint and fell back to a bundled copy of the same data if parsing failed. It read `presets`, but the API's contract named the field `chair_presets`, so parsing always failed and the UI quietly showed the bundled copy. It looked correct, and no error appeared in tests or in the browser. Once a contract is published, diff the field names your client reads against it, and make the fallback route return the same shape as the live one (e.g. `{sweep: null, chair_presets, note}`), so one parser serves both paths. A guess-the-keys parser written before the contract existed (`b.sweep ?? b.chair_sweep ?? ...`) had the same blind spot: the real payload nested the array one level deeper, so nothing drew until it was rewritten against the contract.
