Delete a subsite in Combell Public

What this operation does

Delete a subsite

• DELETEChanges data · Linux hostings/linuxhostings/{domainName}/subsites/{siteName}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Combell Public operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Combell Public operations

• Create a new mysql userPOST · changes data
• Create a new accountPOST · changes data
• Create a new mailboxPOST · changes data
• Create a new mysql databasePOST · changes data
• Create a recordPOST · changes data
• Create a new aliasPOST · changes data
• Add a SSL certificate requestPOST · changes data
• Create a catch-all on the mail zonePOST · changes data

All 75 Combell Public operations

Questions

Can HumDay delete a subsite in Combell Public?

Yes. This operation is published in Combell Public's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Combell Public data?

Yes — this is a DELETE operation, so it changes something in Combell Public. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Combell Public account.

Where this came from

Read from a published API description for Combell Public at api.combell.com/v2/documentation/swagger-v2.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.