Why is complete API coverage required (no missing API)?

Complete API coverage is required — no endpoint may be missing — because API-based templates rely on the API for *everything* they display and do. If any capability lacked an API, a headless front end couldn't perform it, breaking the promise that a custom template can fully drive the store. So the platform commits to exposing its full functionality through the API, which is what makes…

Complete API coverage is required — no endpoint may be missing — because API-based templates rely on the API for *everything* they display and do. If any capability lacked an API, a headless front end couldn't perform it, breaking the promise that a custom template can fully drive the store. So the platform commits to exposing its full functionality through the API, which is what makes genuinely headless, API-based storefronts viable. It also underpins integrations and extensions generally.