API Workflow Coverage
API workflow coverage for create, update, delete, provisioning, restore, and service actions.
This roadmap records operational API coverage that makes sense for a hosting control panel, but was not found as published endpoint files in the deployed build. It exists so developers can understand the intended direction without mistaking undocumented routes for production routes.
Workflow Coverage
| Area | Examples | Status |
|---|---|---|
| Users | Create, update, disable, enable, reset access | Use deployed route documentation. |
| Accounts | Create, suspend, unsuspend, terminate, change package, update limits | Use deployed route documentation. |
| Domains and DNS | Add domain, remove domain, create/update/delete record | Use deployed route documentation. |
| Websites | Create website, update document root, manage redirects, configure runtime | Write workflow guidance. |
| SSL | Request, renew, revoke, force renewal job | Write workflow guidance. |
| Create mailbox, update mailbox, delete mailbox, manage aliases/forwarders | Write workflow guidance. | |
| Databases | Create database, create user, grant/revoke access, export/import | Write workflow guidance. |
| Backups | Create backup, restore backup, queue remote backup | Write workflow guidance. |
| Security | Block/unblock IP, add firewall rule, queue malware scan | Write workflow guidance. |
| Jobs | Queue, retry, cancel, run worker actions | Planned write coverage except current read endpoints. |
How to Use This Roadmap
- Use it for product planning and integration design.
- Do not give customers these URLs as live API instructions.
- When a route is implemented, move it into an available endpoint article and include real request/response examples from source.
- Keep write endpoints auditable and preferably job-backed.