Combell Public API

Name: Combell Public API
Brand: Combell Public API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureNetworkinghmac75 EndpointsREST

For Agents

Manage Combell hosting accounts, domains, DNS records, mailboxes, mail zones, SSL, and Linux hosting settings programmatically via 75 endpoints.

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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

GET STARTED

Start building with Combell Public API

Explore with Jentic

View OpenAPI Document

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.

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 the Jentic vault 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

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Combell HMAC key and secret are stored encrypted in the Jentic vault. Jentic signs each request with the secret at execution and never exposes either value to the agent.

Intent-based discovery

Agents search by intent (e.g., 'add a DNS record') and Jentic returns the matching Combell operation with its parameter schema so the agent can call the right endpoint without browsing docs.

Time to first call

Direct integration: 2-4 days to implement HMAC signing, retries, and the spread of resources. Through Jentic: under 1 hour — search, load schema, execute.

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.

Combell Public API

Connect the Combell Public API to your agent

Capabilities

Start building with Combell Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs