Provision Modoboa domains and mailboxes through supported administration
Use administrator roles and the deployed REST schema to automate hosting resources without bypassing the mail stack's account model.
Reviewed
Modoboa’s REST API automates administration, such as hosting resources exposed by the installed version/extensions. That does not make every account token a transactional sending credential.
Establish the management contract
- Open the REST/OpenAPI reference linked from the official documentation for your deployed release.
- Select the intended administrator role/scope and configure the documented API authentication. Keep the token on a trusted backend.
- Use the supported domain/mailbox operations and validation rules, starting with a controlled domain and quota.
- Inspect resource identity/state before retries so provisioning does not silently duplicate or overwrite an existing account.
Do not issue direct database edits as a shortcut: they can skip extension hooks, permissions, password handling, or generated mail configuration. Use the installed schema rather than inventing endpoint names from another panel.
Verify the provisioned outcome
Confirm the resource is visible to the intended administrator, the mailbox can authenticate, and a controlled message reaches its store. Test that another domain administrator cannot manage it.
Configure SMTP submission through the actual mail services with an appropriately restricted identity. A management API success does not prove mail delivery, DNS verification, or inbox placement. If connecting incoming mail to an application, choose an explicit forwarding/parser contract and preserve tenant boundaries instead of handing the application global panel credentials.