Developers
Hosting your automation can operate
Every Aderlo Cloud account can create its own scoped API keys and be driven from outside — n8n, CI pipelines, plain scripts, or an AI agent. 117 commands cover domains, DNS, mail, databases, FTP, SSL, backups and usage statistics. Most shared hosts in this market give API access to resellers only, or not at all.
Creating an API key
Panel → Advanced Features → Login Keys → Create. Four settings matter:
| Setting | Recommendation |
|---|---|
| Allow Commands | Only what the integration needs. A key for n8n managing DNS has no business reading your mail. |
| Allow Networks | The IP of the machine calling — your n8n server, your CI runner. The key stops working from anywhere else. |
| Allow Login | Off. API-only keys cannot be used to log into the panel if they leak. |
| Expiry | Set one for temporary access — an agency doing a one-off migration does not need a key that outlives the project. |
Key names must be alphanumeric — hyphens and underscores are rejected by the panel.
Authentication
HTTP Basic: username is your hosting account name, password is the API key. Append json=yes to get JSON instead of URL-encoded responses.
BASE="https://web01.aderlo.cloud:2222"
AUTH="youraccount:YOUR_API_KEY"Examples
Each of these was run against a real customer account and returned the response shown.
List your domains
curl -u "$AUTH" "$BASE/CMD_API_SHOW_DOMAINS?json=yes"
# ["yourstore.pl"]Account usage — for monitoring and alerts
curl -u "$AUTH" "$BASE/CMD_API_SHOW_USER_USAGE?json=yes"
# {"bandwidth":"0.0","domainptr":"0","email_deliveries":"0", ...}Read and modify DNS
# read the zone
curl -u "$AUTH" "$BASE/CMD_API_DNS_CONTROL?domain=yourstore.pl&json=yes"
# add an A record
curl -u "$AUTH" "$BASE/CMD_API_DNS_CONTROL" \
-d domain=yourstore.pl -d action=add -d type=A -d name=api -d value=1.2.3.4Create a mailbox
curl -u "$AUTH" "$BASE/CMD_API_EMAIL_POP" \
-d action=create -d domain=yourstore.pl -d user=contact \
-d passwd=... -d passwd2=... -d quota=1024List databases
curl -u "$AUTH" "$BASE/CMD_API_DATABASES?json=yes"Using it from n8n
No dedicated node needed — the standard HTTP Request node does it all:
| Method | GET or POST |
| URL | https://web01.aderlo.cloud:2222/CMD_API_… |
| Authentication | Generic → Basic Auth |
| User / Password | account name / API key — stored in n8n Credentials |
| Query / Body | command parameters plus json=yes |
Keep the key in n8n Credentials, never hardcoded in a node — otherwise it ends up in every workflow export and in your git history.
Two pitfalls worth knowing
error=0 does not always mean it worked
We have observed delete operations answer error=0 without deleting anything. After any state-changing call, make a separate read to verify the result — in n8n that means one extra node, and it is worth it.
Response messages are localised — parse the fields, not the text
Responses are URL-encoded and human-readable messages arrive in the account's panel language. Automation must branch on the error field, never on message strings.
WP-CLI over SSH
Every plan includes jailed SSH with WP-CLI 2.12 — the tool agencies use to script WordPress across many stores:
wp plugin update --all
wp core update
wp db export backup.sql
wp search-replace 'staging.yourstore.pl' 'yourstore.pl'The full list of 117 commands is shown in the panel when creating a key, grouped by area — domains, mail, DNS, databases, files, FTP, SSL, cron and statistics. Pick only what your integration needs; you can always create another key.