infomaniak_add_site_aliases
Bind additional FQDNs, including wildcards like *.example.com, to an existing web hosting site so they serve from the same DocumentRoot — no new site provisioning required.
Instructions
Bind one or more additional FQDNs (including wildcards like *.example.com) to a web hosting site. Lets the site's Apache vhost / DocumentRoot serve those new domains too — no new site provisioning required. Two-phase commit. Asynchronous: returns a progress_id; the alias appears in infomaniak_list_site_aliases after a few seconds of provisioning. Manager-private.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"hosting_id": "<hosting_id>",
"site_id": "<site_id>",
"aliases": "<aliases>"
},
"name": "infomaniak_add_site_aliases"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| aliases | Yes | One or more FQDNs to bind to the site. WILDCARDS ARE ACCEPTED (e.g. `*.evo.broz.be`) — use this pattern to serve any subdomain from a single WordPress install. The DNS for each alias must already point to the hosting's IP, otherwise Apache will respond but the browser will never reach it. | |
| site_id | Yes | ||
| hosting_id | Yes | ||
| confirmation_token | No | Token from the prior plan response. Required on the apply phase only. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||