How is the REST API documented (Swagger), and why is full coverage important?

The platform commits to complete API coverage — every capability is reachable via the API — because API-based (headless) templates and integrations depend on it; a missing endpoint would mean something the front end or an integration simply couldn't do. Full coverage is therefore a design requirement, not a nice-to-have. *(The specific documentation tooling — e.g. Swagger/OpenAPI — is…

The platform commits to complete API coverage — every capability is reachable via the API — because API-based (headless) templates and integrations depend on it; a missing endpoint would mean something the front end or an integration simply couldn't do. Full coverage is therefore a design requirement, not a nice-to-have. *(The specific documentation tooling — e.g. Swagger/OpenAPI — is the standard way to expose and document such an API; confirm it's enabled in your build before stating "Swagger" explicitly, as the system reference emphasizes coverage rather than naming the doc tool.)*