Combell Public API
64
AI ReadinessAI-Aware (B)64/100
Official vendor OpenAPI document · agent-readyCloud InfrastructureNetworkinghmac75 EndpointsREST
For Agents
Manage Combell hosting accounts, domains, DNS records, mailboxes, mail zones, SSL, and Linux hosting settings programmatically via 75 endpoints.
Use for: Register a new domain name on behalf of a customer, Add an A record to an existing DNS zone, Create a new mailbox for a domain, Change the PHP version on a Linux hosting site
Not supported: Does not handle payment processing, end-user customer billing, or third-party DNS providers - use for Combell-hosted domains, mail, and hosting management only.
Combell is a Belgian hosting provider whose Public API lets resellers and customers manage domains, DNS records, Linux and Windows hosting, mailboxes, mail zones, accounts, SSL, and scheduled tasks programmatically. The API exposes 75 endpoints across 58 paths covering domain registration and transfer, DNS CRUD, mailbox provisioning, anti-spam and aliases, PHP and SSL settings on Linux hosting, SSH key management, and reseller account creation. Authentication uses HMAC-signed requests with a customer-issued key and secret per Combell's authorisation documentation.
Install Jentic One Beta
Connect the Combell Public API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Combell Public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcombell.com%2Fcombell" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcombell.com%2Fcombell" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Combell Public API.
Register, transfer, and renew domain names via /domains/registrations, /domains/transfers, and /domains/{domainName}/renew
Create, update, and delete DNS records on a domain via /dns/{domainName}/records
Provision and manage mailboxes including password, autoreply, and autoforward via /mailboxes
Configure mail-zone catch-alls, anti-spam, and aliases via /mailzones/{domainName}
Adjust Linux hosting PHP version, memory limit, and APCu settings via /linuxhostings/{domainName}/phpsettings
Manage SSH keys, scheduled tasks, and Let's Encrypt SSL on Linux hostings
Create reseller accounts and view account details via /accounts
Use Cases
Patterns agents use Combell Public API for, with concrete tasks.
★ White-Label Hosting Resale
Resell Combell hosting through a custom storefront by orchestrating /accounts (create reseller accounts), /domains/registrations (register the customer's domain), and /linuxhostings (provision the hosting). The API covers the full provisioning lifecycle so a reseller portal can issue a hosting plan in minutes without touching Combell's UI. Pair with /mailboxes to set up the customer's first email account during onboarding.
Call POST /accounts to create a reseller account, POST /domains/registrations for the customer's domain, then POST /mailboxes to create their first mailbox
DNS Automation
Automate DNS management across many domains by calling GET /dns/{domainName}/records to read the current zone and POST/PUT/DELETE /dns/{domainName}/records to apply changes. A devops platform can keep DNS in sync with a git-managed source of truth, applying drift corrections on a schedule. The API supports common record types so most multi-domain rollouts can be scripted.
For each domain in a tracked list, call GET /dns/{domainName}/records, diff against the desired state, and call POST/PUT/DELETE on /dns/{domainName}/records to converge
Email Provisioning at Scale
Provision mailboxes for a customer's full team in a single workflow by calling POST /mailboxes for each user, configuring autoreply and autoforward via PUT /mailboxes/{mailboxName}/autoreply and /autoforward, and managing aliases through /mailzones/{domainName}/aliases. This pattern fits agencies onboarding new clients who need a turnkey email setup.
For each user in a CSV, call POST /mailboxes with email and password, then POST /mailzones/{domainName}/aliases for any aliases the user needs
Site Configuration Audits
Audit Linux hosting configurations across a customer base by reading PHP version (/linuxhostings/{domainName}/phpsettings/availableversions), GZIP compression, HTTP/2 status, and SSL configuration. A managed-service provider can flag sites running outdated PHP or missing Let's Encrypt and remediate via the corresponding PUT endpoints. This keeps compliance and security baselines current.
For each linux hosting, GET /linuxhostings/{domainName}/phpsettings/availableversions and PUT /linuxhostings/{domainName}/phpsettings/version to bring outdated sites up to a target PHP version
AI Agent Hosting Operations via Jentic
Let an AI agent operate a Combell hosting account by searching Jentic for the operation it needs (register a domain, add a DNS record, create a mailbox) and executing it. Combell's HMAC credentials live in your Jentic One instance and are signed into requests at execution so the agent never sees the key or secret.
Use Jentic to search 'add a DNS record', load the POST /dns/{domainName}/records schema, and execute it with the desired record type and value
Key Endpoints
75 endpoints — combell is a belgian hosting provider whose public api lets resellers and customers manage domains, dns records, linux and windows hosting, mailboxes, mail zones, accounts, ssl, and scheduled tasks programmatically.
METHOD
PATH
DESCRIPTION
POST
/domains/registrations
Register a new domain
POST
/dns/{domainName}/records
Create a DNS record
POST
/mailboxes
Create a new mailbox
POST
/mailzones/{domainName}/aliases
Create a mail-zone alias
PUT
/linuxhostings/{domainName}/phpsettings/version
Change PHP version
PUT
/linuxhostings/{domainName}/sslsettings/{hostname}/letsencrypt
Configure Let's Encrypt SSL
POST
/accounts
Create a reseller account
POST
/domains/registrations
Register a new domain
POST
/dns/{domainName}/records
Create a DNS record
POST
/mailboxes
Create a new mailbox
POST
/mailzones/{domainName}/aliases
Create a mail-zone alias
PUT
/linuxhostings/{domainName}/phpsettings/version
Change PHP version
PUT
/linuxhostings/{domainName}/sslsettings/{hostname}/letsencrypt
Configure Let's Encrypt SSL
POST
/accounts
Create a reseller account
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
P
Public Api
- AI-Aware (B)64/100
60
Foundational Compliance56
Developer Experience & Jentic Compatibility56
AI-Readiness & Agent Experience90
Agent Usability100
Security51
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
60
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: B-Signals: 4
41%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
32%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
93%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
56
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
68%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
56%
Summary Coverage
Coverage of summaries across operations/tags/info.
90
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
90%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
51
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C-Signals: 1
51%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Combell by hand means computing an HMAC signature from your key and secret for every request and handling more than seventy domain, DNS, mail, and hosting endpoints yourself. Through Jentic you install once, import Combell from the API Directory, store the key and secret once, and your agent calls it.
Permission scoping
Combell puts the domain name in the URL path (/dns/{domainName}/records, /linuxhostings/{domainName}/...), so a rule can pin your agent to one domain: it manages only that domain and nothing else. You choose the operations it may call, so actions like registering domains or creating accounts are not included unless you add them.
Credential isolation
Your Combell HMAC key and secret are stored once, encrypted, by your own Jentic One instance and the request is signed at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'add a DNS record' or 'create a mailbox', and Jentic returns the matching Combell operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Combell Public API through Jentic.
What authentication does the Combell Public API use?
Combell uses HMAC-signed requests with a key and secret issued from the customer area. Each request must be signed per Combell's authorisation documentation. Through Jentic the key and secret live in the encrypted vault and the signed Authorization header is generated at execution so neither value enters the agent's prompt.
Can I register a new domain through the Combell Public API?
Yes. POST /domains/registrations registers a new domain on behalf of the authenticated reseller account. Use POST /domains/transfers to transfer in an existing domain and PUT /domains/{domainName}/renew to renew one.
How do I manage DNS records with the Combell Public API?
GET /dns/{domainName}/records returns the zone and POST creates a record. Individual records are addressed by recordId for PUT (edit) and DELETE. The same endpoints serve A, AAAA, CNAME, MX, TXT, and other supported record types.
What are the rate limits for the Combell Public API?
The OpenAPI spec does not enumerate explicit rate limits. Combell enforces fair-use limits per account; 401 and 403 responses indicate authorisation issues, while 429 indicates throttling. Consult your Combell customer area for current limits.
How do I create a mailbox for a domain through Jentic?
Search Jentic for 'create a mailbox', load the POST /mailboxes schema, and execute it with the email address, password, and quota. Jentic signs the HMAC Authorization header from vault credentials and returns the created mailbox.
Can I configure Let's Encrypt SSL through the API?
Yes. PUT /linuxhostings/{domainName}/sslsettings/{hostname}/letsencrypt provisions or updates a Let's Encrypt certificate for a hostname on a Linux hosting site. Pair with /autoredirect to force HTTPS once the certificate is installed.
Can I limit what my agent is allowed to do with the Combell Public API?
Yes. Because you run Jentic One yourself, your own rules decide which Combell operations and credentials the agent may use. Combell puts the domain name in the URL path (for example /dns/{domainName}/records and /linuxhostings/{domainName}/...), so a rule can pin the agent to a single domain and let it manage only that domain's DNS, mailboxes, and hosting settings. You also choose the exact operations it can call, so high-impact actions like registering domains via POST /domains/registrations or creating reseller accounts via POST /accounts stay off limits until you grant them.
GET STARTED