Backward compatibility means an existing consumer still works after a new API version is deployed. Adding an optional response field is often tolerated, while removing or changing a required field may break old code. The actual result depends on consumer parsers and validation rules.
The demo passes an optional addition and fails when required id disappears. Use consumer contract tests and usage data to judge impact, and plan migration for breaking changes.
When to use
Check it before changing request or response schemas of a live API.