canonical: https://jentic.com/apis/alwaysdata/alwaysdata

# Alwaysdata API

Jentic publishes the only available OpenAPI specification for Alwaysdata API, keeping it validated and agent-ready. Alwaysdata is a French web-hosting provider, and this REST API exposes 38 HTTP Basic-authenticated endpoints for managing hosting accounts, domains, DNS records, websites, mailboxes, databases, and SSL certificates. Teams use it to automate provisioning, register and update domains, manage DNS at the record level, and orchestrate site and database lifecycle without logging into the control panel.

## For AI agents

Manage Alwaysdata hosting: accounts, domains, DNS records, websites, mailboxes, databases, and SSL certificates through 38 HTTP Basic-authenticated endpoints. Useful for agents automating provisioning and DNS changes.

## Scope

Does not provision cloud VMs, run container orchestration, or manage CDN edge configuration - use only for managing Alwaysdata hosting accounts, domains, DNS, websites, mailboxes, databases, and certificates.

## Capabilities

- List and update hosting accounts via /account/
- Register, list, and delete domains through /domain/
- Create, update, and delete DNS records on managed domains via /record/
- Provision and manage hosted websites and their configuration
- Create, list, and delete mailboxes attached to managed domains
- Provision and manage databases and database users
- Issue and manage SSL certificates tied to a hosted domain

## Use cases

### Automated DNS Record Management

DevOps teams using Alwaysdata for DNS hosting script record changes through /record/ instead of clicking through the control panel. The endpoint exposes full CRUD on A, AAAA, CNAME, MX, and TXT records, which is enough to support deployments that need to flip records as part of cutover or to provision per-environment subdomains automatically.

Example prompt: POST /record/ with type=A, name='app', value='203.0.113.10', and the parent domain id, then GET /record/{id}/ to confirm propagation.

### Domain Lifecycle Automation

Agencies and SaaS providers manage many client domains by automating registration, transfer, and deletion through /domain/. Combined with the DNS, mailbox, and SSL endpoints, the API supports a complete add-domain workflow: register, configure DNS, provision mailboxes, and issue an SSL certificate from a single script.

Example prompt: POST /domain/ to register example.com, then POST /record/ to add the A and MX records, then trigger SSL issuance for the new domain.

### Hosted Mailbox Provisioning

Teams using Alwaysdata for email automate mailbox creation when new staff arrive instead of sharing the control panel. The API surfaces mailbox CRUD tied to the parent domain, and DNS endpoints sit alongside it so deliverability records (MX, SPF in TXT) can be updated in the same script.

Example prompt: POST a mailbox creation request for the new hire's address against the appropriate domain id, then verify the MX record is in place via GET /record/.

### AI Agent Hosting Operator via Jentic

An AI ops agent built on Jentic can take 'point staging.example.com to 203.0.113.10' and resolve it to the right /record/ create call without the agent ever holding the Alwaysdata Basic auth credential. your Jentic One instance stores the credential and Jentic injects the Authorization header at call time.

Example prompt: Search Jentic for 'create a DNS record', load the POST /record/ schema, and execute it with type=A, name='staging', value=the supplied IP, and the matching domain id.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /account/ | List hosting accounts |
| GET | /domain/ | List managed domains |
| POST | /domain/ | Register or add a domain |
| DELETE | /domain/{id}/ | Delete a domain |
| GET | /record/ | List DNS records |
| POST | /record/ | Create a DNS record |
| PUT | /record/{id}/ | Update an existing DNS record |
| DELETE | /record/{id}/ | Delete a DNS record |

## Key resources

- **Account** — List and update Alwaysdata hosting accounts
- **Domain** — Register, manage, and delete domains
- **Record** — Manage DNS records on hosted domains
- **Site** — Provision and configure hosted websites
- **Mailbox** — Manage mailboxes tied to hosted domains
- **Database** — Provision and manage databases and database users
- **SSL Certificate** — Issue and manage SSL certificates

## Why Jentic

- **Setup:** Wiring the Alwaysdata API by hand means encoding its HTTP basic credentials, targeting api.alwaysdata.com/v1, and coordinating account, domain, DNS record, and mailbox calls yourself. Through Jentic you install once, import the Alwaysdata API from the API Directory, store the basic credential once, and your agent calls it.
- **Permission scoping:** The Alwaysdata API puts the resource id in the URL path (/domain/{id}/, /record/{id}/), so a rule can pin your agent to one domain or DNS record. You choose the operations it may call, so deleting a domain or record is not included unless you add it.
- **Credential handling:** Your Alwaysdata basic credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list domains' or 'add a DNS record', and Jentic returns the matching Alwaysdata operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudflare API** — Global DNS, CDN, and edge security platform with extensive automation
- **DigitalOcean API** — Cloud infrastructure provider with Droplets, managed databases, and DNS
- **Linode API** — Cloud compute, networking, and DNS from Akamai-owned Linode
- **OpenAI API** — Use a language model alongside Alwaysdata to plan or summarise infrastructure changes

## FAQ

### Why is there no official OpenAPI spec for Alwaysdata API?

Alwaysdata does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Alwaysdata API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Alwaysdata API use?

Alwaysdata uses HTTP Basic authentication with an account-issued API key as the username. Through Jentic, the credential is stored encrypted in your Jentic One instance and the Authorization header is injected at call time.

### Can I create DNS records with the Alwaysdata API?

Yes. POST to /record/ with the record type, name, value, and parent domain id to create A, AAAA, CNAME, MX, or TXT records. PUT /record/{id}/ updates an existing record and DELETE /record/{id}/ removes one.

### What are the rate limits for the Alwaysdata API?

Specific limits are not in the spec. Treat the API as account-throttled and add retry-with-backoff for 429 responses. Batch DNS changes to limit bursts during deploy windows.

### How do I add a domain through Jentic?

Run pip install jentic and search with 'register a domain in Alwaysdata'. Load the POST /domain/ schema and execute it with the domain name. Follow up with POST /record/ to configure DNS for the new domain.

### Does the Alwaysdata API let me issue SSL certificates?

Yes. The SSL certificate endpoints expose listing, issuing, and deletion tied to a hosted domain id, so you can request a certificate as part of the same automation that adds the domain and DNS records.

### Can I limit what my agent is allowed to do with the Alwaysdata API?

Yes. Because you self-host Jentic One, your own rules decide which Alwaysdata operations and credentials the agent may use. The API puts the resource id in the URL path, such as /domain/{id}/ and /record/{id}/, so you can pin the agent to a single domain or DNS record. You also choose which operations it may call, so destructive calls like DELETE /domain/{id}/ or DELETE /record/{id}/ stay off limits unless you explicitly allow them.