Developers

A public API and MCP server for the Ex2 catalogue

Plans, prices, domain names and their availability, and what moving a site to Ex2 takes, in JSON for your code or as tools for AI assistants: free, read-only, no key. Ex2 customers can also connect their own account.

Overview

Four ways in, all JSON over HTTPS. The catalogue is public; your account needs you to sign in.

InterfaceAddressSign-inFor
Catalogue APIhttps://www.ex2.com/api/v1NonePlans, prices, domain names and site migration, in your code.
Public MCP serverhttps://www.ex2.com/mcpNoneThe same catalogue as tools for AI assistants.
Account MCP serverhttps://api.ex2.com/mcp/accountOAuth 2.1 or API tokenYour Ex2 account in an AI assistant.
Account APIhttps://api.ex2.com/api/v1/accountOAuth 2.1 or API tokenYour Ex2 account in your code and agents.

The two MCP servers and the two APIs answer from the same code: a tool and its endpoint give the same answer. The account server and the account API share one sign-in, the same checks and one audit log.

Connect an AI assistant

With the MCP server (Model Context Protocol), an assistant answers with today’s plans and prices and real order links, instead of figures it remembers.

Claude Code

In a terminal:

claude mcp add --transport http ex2 https://www.ex2.com/mcp

Claude, ChatGPT and other apps

Add a custom connector (a remote MCP server) with this URL, without authentication:

https://www.ex2.com/mcp

Cursor, VS Code and other editors

In the editor’s MCP configuration, for example Cursor’s .cursor/mcp.json:

{
  "mcpServers": {
    "ex2": { "url": "https://www.ex2.com/mcp" }
  }
}

Streamable HTTP, no session, no authentication. Protocol versions 2025-03-26, 2025-06-18, 2025-11-25, 2026-07-28. Its 7 tools.

Your Ex2 account in your AI assistant

A second MCP server, for Ex2 customers: once you sign in, your assistant can read your account (services, domain names, invoices, support tickets and, on Ex2’s servers, your hosting) and answer your questions about it, and act for you only where you allow it when connecting. You can disconnect it at any time.

Claude, ChatGPT and other apps

Add a custom connector with this URL. The first time, the app opens Ex2’s sign-in page:

https://api.ex2.com/mcp/account

Claude Code

In a terminal, then /mcp in Claude Code to sign in:

claude mcp add --transport http ex2-account https://api.ex2.com/mcp/account

Cursor, VS Code and other editors

In the editor’s MCP configuration; the editor asks you to sign in:

{
  "mcpServers": {
    "ex2-account": { "url": "https://api.ex2.com/mcp/account" }
  }
}

The account server has the catalogue tools and the account’s. The tools that read and the quotes change nothing. The others act only where you allowed it when connecting, one box for each kind of action: billing (orders, renewals, plan changes, cancellations, invoices); domain names (nameservers, lock, transfer away); DNS records; mailboxes and forwarders; WordPress (updates, installs, staging copies); sites (databases, subdomains, PHP, cron jobs); archives of a site or the account; SSH keys; support tickets; restores from backups. An order, a renewal or a plan change makes an invoice; pay_invoice pays one from your credit balance, then your saved card, only within the monthly amount you set on the connection. None can read your passwords, your payment details or a domain’s transfer code. Its 80 account tools.

You decide

Before you log in, Ex2’s own page names the application and lists what it will read, with a box for each kind of action: no action is allowed unless you tick its box. You set the monthly amount it may pay invoices with, and can limit it to one service or domain name. You log in with your Ex2 client area login, and choose the account if your login manages several.

Your permissions apply

A contact of an account only sees what their client area permissions allow, checked again at every request. Your passwords, payment details and ticket messages are never read; a password made for something new (a mailbox, a database) is given once.

Disconnect at any time

See the assistants connected to your account and disconnect any of them on the connected assistants page. Access lasts an hour and is renewed only while the connection exists.

Authentication

The catalogue is public: no key, no account. Your own account needs your Ex2 login, through the sign-in page, and an assistant or a token acts on it only where you ticked a box. It pays an invoice only from your credit balance or saved card, within the monthly amount you set; otherwise you pay it in the client area.

API tokens, for your own scripts

Signed in to Ex2, make a token on the connected assistants page: a name, one of your accounts, a lifetime of 30, 90 or 365 days, and the actions it may take. It is shown once: send it as a bearer token to the account API or the account server. Up to 20 active per login, each disconnected there at any time.

curl https://api.ex2.com/api/v1/account/services \
  -H "Authorization: Bearer ex2pat_…"

Sign-in for applications (OAuth 2.1)

An application registers itself, with a Client ID Metadata Document or at https://api.ex2.com/oauth/register (RFC 7591), then sends the customer to Ex2’s sign-in: an authorization code with PKCE (S256), naming the resource it wants, https://api.ex2.com/mcp/account for the account server or https://api.ex2.com/api/v1/account for the account API (RFC 8707). A token works at its own resource only. Access tokens last 60 minutes; refresh tokens 30 days, renewed at each use. AI assistants do all of this by themselves.

Metadata: the authorization server’s at https://api.ex2.com/.well-known/oauth-authorization-server (RFC 8414), each resource’s under /.well-known/oauth-protected-resource, like https://api.ex2.com/.well-known/oauth-protected-resource/api/v1/account (RFC 9728). A call without a token answers 401, its WWW-Authenticate header pointing there.

Scopes

Every token reads the account, quotes included. Each kind of action needs its own scope, which only the customer’s tick grants, on the sign-in page or on the token’s form. Without it, 403 insufficient_scope, and the account server does not list the tool.

ScopeAllows
account:readReading the account: services, domain names, invoices, tickets and hosting, with the quotes and previews. Every token has it.
account:billingOrders, renewals, automatic renewal, plan changes and cancellations, and paying invoices within the monthly amount set on the connection.
account:domainsA domain name’s nameservers and lock, and its transfer away.
account:dnsDNS records, on Ex2’s servers and at the registrar.
account:mailMailboxes and forwarders.
account:wordpressWordPress updates, installs, database restores and staging copies.
account:sitesDatabases, subdomains, addon domains, aliases, PHP, cron jobs and SSL checks.
account:exportArchives of a site or of a whole hosting account, and their download.
account:sshSSH keys.
account:ticketsOpening support tickets and replying to them.
account:backupsBackups on demand and restores.

The customer can also limit a connection or a token to one service or one domain name: anything else then answers 403 outside_limit.

Tools

The 87 tools of the two MCP servers, by what they cover. Under each, the HTTP endpoint that does the same: the catalogue API’s on www.ex2.com, the account API’s on api.ex2.com.

Public no sign-in, on both servers Reads reads your account or quotes, changes nothing Changes acts on your account, only with its scope

Catalogue

On both servers, without signing in. All read-only: they cannot order or change anything.

  • list_product_linesPublic

    The product lines (green hosting, WordPress, email, VPS…) with their pages and plan ids.

    GET/api/v1

  • list_plansPublic

    Plans with their prices per billing cycle, first-year discount and main features; all of them or one product line.

    GET/api/v1/plans

  • get_planPublic

    One plan with its full specification table.

    GET/api/v1/plans/{id}

  • compare_plansPublic

    Two to ten plans side by side, one row per specification.

    GET/api/v1/compare

  • get_domain_pricingPublic

    One-year register, transfer and renewal prices per domain extension.

    GET/api/v1/domains/pricing

  • check_domainPublic

    Whether a domain name can be registered now, its prices and the link to order it (or to transfer it, when taken).

    GET/api/v1/domains/availability

  • quote_migrationPublic

    Moving a site to Ex2: free, 24 hours for a simple site and 48 at most, what moves, what our team needs and how to ask.

    GET/api/v1/migration

Your account

What the account holds, read-only.

  • get_my_accountReads

    Your client account: name, company, email, country, currency and credit balance.

    GET/api/v1/account

  • list_my_servicesReads

    Your hosting plans and other services: status, billing cycle, next due date and price, with the link to manage each one.

    GET/api/v1/account/services

  • list_my_domainsReads

    Your domain names: status, expiry date, renewal price and whether they renew automatically.

    GET/api/v1/account/domains

  • list_my_invoicesReads

    Your invoices, the unpaid ones by default (or paid, or all), most recent first: number, dates, total, whether one is overdue, the link to pay it and, when you ask for it, a link to its PDF.

    GET/api/v1/account/invoices

  • list_my_ticketsReads

    Your support tickets: subject, department, status and date of the last reply. Never the messages themselves.

    GET/api/v1/account/tickets

Billing and orders

Quotes, orders, renewals, plan changes and cancellations; each purchase makes an invoice.

  • quote_domain_orderReads

    Whether a domain name can be registered or transferred in, its price, the registry's rules (.ca, .fr) and the terms to accept. Changes nothing.

    GET/api/v1/account/orders/domain

  • order_domainChanges

    Orders a domain name, registration or transfer in: an order and its invoice, once you accept the price and the terms.

    POST/api/v1/account/orders/domainScope account:billing

  • quote_plan_orderReads

    The price of a plan for your site, first payment and renewal, and the terms to accept. Changes nothing.

    GET/api/v1/account/orders/plan

  • order_planChanges

    Orders a plan for your site: an order and its invoice; Ex2 sets it up once it is paid.

    POST/api/v1/account/orders/planScope account:billing

  • set_domain_auto_renewChanges

    Turns the automatic renewal of one of your domain names on or off.

    POST/api/v1/account/domains/{id}/auto_renewScope account:billing

  • renew_domainChanges

    Renews a domain name for 1 to 10 years: an order and its invoice, which you pay as usual.

    POST/api/v1/account/domains/{id}/renewScope account:billing

  • quote_plan_changeReads

    What moving a service to another plan would cost now and at renewal. Changes nothing.

    GET/api/v1/account/services/{id}/plan_change

  • change_planChanges

    Moves a service to another plan; an amount due makes an invoice.

    POST/api/v1/account/services/{id}/plan_changeScope account:billing

  • cancel_serviceChanges

    Cancels a service, at the end of its billing period or immediately, after saying what would happen.

    GET/api/v1/account/services/{id}/cancellationPOST/api/v1/account/services/{id}/cancellationScope account:billing

  • pay_invoiceChanges

    Pays an unpaid invoice with the credit balance, then the saved card, within the monthly amount you set on the connection.

    POST/api/v1/account/invoice_paymentScope account:billing

Domain names

A domain name’s nameservers, lock and transfer away.

  • get_domain_registrar_settingsReads

    A domain name's nameservers and whether it is locked against transfers.

    GET/api/v1/account/domains/{id}/registrar

  • set_domain_nameserversChanges

    Points a domain name to other nameservers.

    POST/api/v1/account/domains/{id}/nameserversScope account:domains

  • set_domain_lockChanges

    Locks or unlocks a domain name at its registrar.

    POST/api/v1/account/domains/{id}/lockScope account:domains

  • transfer_domain_outChanges

    Prepares a domain name's move to another registrar: unlocks it and emails its transfer code to you, never to the assistant.

    GET/api/v1/account/domains/{id}/transfer_outPOST/api/v1/account/domains/{id}/transfer_outScope account:domains

DNS

The DNS zones of a hosting service on Ex2’s servers, and of a domain name whose DNS is at the registrar.

  • list_dns_zonesReads

    The DNS zones of a hosting service on Ex2's servers.

    GET/api/v1/account/services/{id}/dns

  • get_dns_zoneReads

    The records of a DNS zone: MX, SPF, DKIM and DMARC among them.

    GET/api/v1/account/services/{id}/dns/{zone}

  • change_dns_recordsChanges

    Adds, changes and removes DNS records of a zone, in one go (not those carrying the mail of the account's addresses).

    POST/api/v1/account/services/{id}/dns/{zone}Scope account:dns

  • export_dns_zoneReads

    A DNS zone as a zone file, to keep or move elsewhere.

    GET/api/v1/account/services/{id}/dns/{zone}/export

  • get_domain_dns_zoneReads

    The DNS zone of a domain name whose DNS is at the registrar (no hosting), with its records.

    GET/api/v1/account/domains/{id}/dns

  • change_domain_dns_recordsChanges

    Adds, changes and removes the DNS records of a domain name at the registrar, in one go (not those carrying the mail of the account's addresses).

    POST/api/v1/account/domains/{id}/dnsScope account:dns

  • export_domain_dns_zoneReads

    A domain name's DNS zone at the registrar as a zone file.

    GET/api/v1/account/domains/{id}/dns_export

Diagnostics

Certificates, resource use and error logs of a hosting service.

  • get_service_sslReads

    The SSL certificates of a service’s sites and when they expire, whether AutoSSL is checking them, and the domains it could not cover, with the reason.

    GET/api/v1/account/services/{id}/ssl

  • get_service_usageReads

    What a service uses of its plan: disk, bandwidth, databases, mailboxes.

    GET/api/v1/account/services/{id}/usage

  • get_site_errorsReads

    The latest errors of a site, from the web server's log.

    GET/api/v1/account/services/{id}/errors

  • get_php_errorsReads

    The latest lines of a site's PHP error log.

    GET/api/v1/account/services/{id}/php_errors

Email

Mailboxes, forwarders, and the SPF, DKIM and DMARC of a hosting service’s domains.

  • list_mailboxesReads

    The mailboxes of a hosting service: address, space used and limit.

    GET/api/v1/account/services/{id}/mailboxes

  • create_mailboxChanges

    Creates a mailbox; its password, made by Ex2, is answered once.

    POST/api/v1/account/services/{id}/mailboxesScope account:mail

  • change_mailboxChanges

    Gives a mailbox a new password or size limit.

    POST/api/v1/account/services/{id}/mailbox_changesScope account:mail

  • delete_mailboxChanges

    Deletes a mailbox and its messages, after a preview.

    GET/api/v1/account/services/{id}/mailbox_deletionPOST/api/v1/account/services/{id}/mailbox_deletionScope account:mail

  • list_forwardersReads

    The forwarders of a hosting service's domains.

    GET/api/v1/account/services/{id}/forwarders

  • add_forwarderChanges

    Sends an address's mail on to another address.

    POST/api/v1/account/services/{id}/forwardersScope account:mail

  • remove_forwarderChanges

    Stops a forwarder.

    POST/api/v1/account/services/{id}/forwarder_removalScope account:mail

  • get_mail_authenticationReads

    Whether each domain's SPF, DKIM and DMARC are in place.

    GET/api/v1/account/services/{id}/mail_authentication

WordPress

WordPress sites: updates, installs, database copies and staging copies.

  • list_wordpress_sitesReads

    The WordPress sites of a hosting service, with their versions.

    GET/api/v1/account/services/{id}/wordpress

  • get_wordpress_statusReads

    A site's WordPress, plugins and themes, with the updates offered.

    GET/api/v1/account/services/{id}/wordpress_status

  • update_wordpressChanges

    Updates WordPress, plugins or themes as a job, after a copy of the database.

    POST/api/v1/account/services/{id}/wordpress_updateScope account:wordpress

  • install_wordpressChanges

    Installs WordPress on a site whose folder is empty, as a job, with its database; the administrator's password is shown once, or set by the customer where the service holds the account's mail.

    POST/api/v1/account/services/{id}/wordpress_installScope account:wordpress

  • list_wordpress_copiesReads

    The copies of a WordPress site's database made before an update or a restore.

    GET/api/v1/account/services/{id}/wordpress_copies

  • restore_wordpress_databaseChanges

    Puts a WordPress site's database back as one of its copies was, after a new copy.

    POST/api/v1/account/services/{id}/wordpress_restoreScope account:wordpress

  • list_stagingsReads

    The staging copies of your WordPress sites, each with its live site, its address and its database.

    GET/api/v1/account/services/{id}/wordpress_staging

  • create_stagingChanges

    Copies a WordPress site to a staging subdomain, as a job, with a database of its own, to try changes away from the live site; search engines are asked not to index it. On Ex2's recent servers.

    POST/api/v1/account/services/{id}/wordpress_stagingScope account:wordpress

  • push_stagingChanges

    Puts a staging copy's files, database or both live, as a job, after a copy of the live database; with the database, what changed on the live site since the copy is lost. On Ex2's recent servers.

    POST/api/v1/account/services/{id}/wordpress_staging_pushScope account:wordpress

  • delete_stagingChanges

    Deletes a staging copy's files and database; its subdomain stays.

    POST/api/v1/account/services/{id}/wordpress_staging_removalScope account:wordpress

Sites

Databases, subdomains, addon domains, aliases, PHP, cron jobs and SSL of a hosting service.

  • list_databasesReads

    The databases of a hosting service, with their users.

    GET/api/v1/account/services/{id}/databases

  • create_databaseChanges

    Creates a database and its user; the password is answered once.

    POST/api/v1/account/services/{id}/databasesScope account:sites

  • change_database_passwordChanges

    Gives a database user a new password, answered once.

    POST/api/v1/account/services/{id}/database_passwordScope account:sites

  • list_subdomainsReads

    The subdomains of a hosting service.

    GET/api/v1/account/services/{id}/subdomains

  • create_subdomainChanges

    Creates a subdomain with its folder and DNS record.

    POST/api/v1/account/services/{id}/subdomainsScope account:sites

  • list_addon_domainsReads

    The addon domains of a hosting service, with their folders.

    GET/api/v1/account/services/{id}/addon_domains

  • add_addon_domainChanges

    Adds one of your domain names at Ex2 to a hosting service as a site of its own.

    POST/api/v1/account/services/{id}/addon_domainsScope account:sites

  • list_domain_aliasesReads

    The aliases (parked domains) of a hosting service.

    GET/api/v1/account/services/{id}/domain_aliases

  • add_domain_aliasChanges

    Makes one of your domain names at Ex2 show a hosting service's main site.

    POST/api/v1/account/services/{id}/domain_aliasesScope account:sites

  • list_php_versionsReads

    The PHP versions installed, and each site's.

    GET/api/v1/account/services/{id}/php

  • set_php_versionChanges

    Moves a site to another PHP version.

    POST/api/v1/account/services/{id}/phpScope account:sites

  • get_php_settingsReads

    The PHP settings of a hosting service (memory, upload size, time limit...) and the values allowed.

    GET/api/v1/account/services/{id}/php_settings

  • request_ssl_certificatesChanges

    Starts AutoSSL's check of a hosting service now: it issues or renews its sites' certificates.

    POST/api/v1/account/services/{id}/sslScope account:sites

  • set_php_settingsChanges

    Changes PHP settings of a hosting service, for all its sites.

    POST/api/v1/account/services/{id}/php_settingsScope account:sites

  • list_cron_jobsReads

    The cron jobs of a hosting service, and what those made through the API run.

    GET/api/v1/account/services/{id}/cron_jobs

  • add_cron_jobChanges

    Schedules a PHP script or a call to one of the site's addresses (every 5 minutes at most).

    POST/api/v1/account/services/{id}/cron_jobsScope account:sites

  • remove_cron_jobChanges

    Removes a cron job made through the API.

    POST/api/v1/account/services/{id}/cron_job_removalScope account:sites

Archives

Archives of a site or of a whole hosting account, to keep or to move elsewhere.

  • export_siteChanges

    Archives a site's folder and WordPress database as a job, to download for a week.

    POST/api/v1/account/services/{id}/exportsScope account:export

  • export_accountChanges

    Archives a whole hosting account as a job (files, databases, DNS zones; never the mail), to move it elsewhere.

    POST/api/v1/account/services/{id}/account_exportsScope account:export

  • list_site_exportsReads

    The archives of a hosting service's sites, with their download address.

    GET/api/v1/account/services/{id}/exportsGET/api/v1/account/services/{id}/exports/{name}

Jobs

Updates, archives and backups run as jobs: follow one here, or with a webhook.

  • get_jobReads

    Where a job stands, step by step.

    GET/api/v1/account/services/{id}/jobs

SSH

The keys that may log in to a hosting service over SSH.

  • list_ssh_keysReads

    The SSH keys of a hosting service, with their fingerprints.

    GET/api/v1/account/services/{id}/ssh_keys

  • add_ssh_keyChanges

    Authorizes a public key to log in to a hosting service over SSH.

    POST/api/v1/account/services/{id}/ssh_keysScope account:ssh

  • remove_ssh_keyChanges

    Takes an SSH key away from a hosting service.

    POST/api/v1/account/services/{id}/ssh_key_removalScope account:ssh

Backups

The backups of a hosting service, and what to restore from them.

  • list_backupsReads

    The backups of a hosting service, newest first, and what each holds.

    GET/api/v1/account/services/{id}/backups

  • get_backupReads

    The parts of one backup: the home folder, each database, the mail and the others.

    GET/api/v1/account/services/{id}/backup_parts

  • backup_nowChanges

    Makes a backup of a hosting service now, as a job.

    POST/api/v1/account/services/{id}/backupsScope account:backups

  • restore_backupChanges

    Puts files of a hosting service, or one of its databases, back as they were in a backup, as a job.

    POST/api/v1/account/services/{id}/backup_restoresScope account:backups

Support tickets

Ex2’s support, in the customer’s name.

  • list_support_departmentsReads

    The departments of Ex2's support a ticket can go to.

    GET/api/v1/account/support_departments

  • open_ticketChanges

    Opens a support ticket in your name, about a service or a domain name, with a note naming the assistant and what it last did.

    POST/api/v1/account/ticketsScope account:tickets

  • reply_to_ticketChanges

    Adds your reply to one of your tickets. The answers come by email and in the client area.

    POST/api/v1/account/tickets/{ticket}/repliesScope account:tickets

The catalogue API

JSON over HTTPS, GET only, open to any origin (CORS). Every answer names its currency; amounts exclude taxes.

EndpointAnswerTry it
GET/api/v1What the API offers, its parameters and the product lines with their plan ids.Try it
GET/api/v1/plansEvery plan with its prices, first-year discount, features and order link. line=email keeps one product line.Try it
GET/api/v1/plans/{id}One plan, with its specification table.Try it
GET/api/v1/compareTwo to ten plans side by side: plans=id1,id2.Try it
GET/api/v1/domains/pricingOne-year register, transfer and renewal price per extension: tld=com,ca or all of them.Try it
GET/api/v1/domains/availabilityWhether domain=… can be registered now, its prices and the cart link.Try it
GET/api/v1/migrationMoving a site to Ex2: free, 24 hours for a simple site and 48 at most, what moves, what our team needs and how to ask.Try it
GET/api/v1/statusWhether the catalogue API, the MCP servers and the account API work right now, and which account actions are on.Try it

Parameters, where an endpoint takes them: currency (CAD, EUR or USD; USD by default) and lang (en or fr; en by default).

The OpenAPI 3.1 description of the API, to import into a custom GPT (Actions), Postman or a code generator:

https://www.ex2.com/api/v1/openapi.json

Example

The price of a .com, in your currency (a live answer):

curl "https://www.ex2.com/api/v1/domains/pricing?tld=com&currency=USD"
{
    "currency": "USD",
    "period_years": 1,
    "order_url": "https://www.ex2.com/clients/cart.php?a=add&domain=register&currency=7&language=english",
    "domains": [
        {
            "tld": ".com",
            "register": 13.25,
            "transfer": 13.25,
            "renew": 15.46
        }
    ]
}

The account API

The same account as the account server, over HTTP, for agents and scripts that do not use MCP.

At https://api.ex2.com/api/v1/account, behind the same sign-in as the account server (OAuth 2.1, with this address as the resource). Its OpenAPI description lists the endpoints: the account, services, domain names, invoices with their PDF, tickets, the same actions as the tools, and the audit log of what each connection did. For your own scripts, make an API token on the connected assistants page, ticking only the actions it needs.

EndpointAnswer
GET/api/v1/accountThe account: name, company, email, country, currency and credit balance.
GET/api/v1/account/servicesHosting plans and other services: status=active (default) or all, and domain=… for one domain name.
GET/api/v1/account/domainsDomain names with their dates, renewal price and automatic renewal: status=active (default) or all, and domain=….
GET/api/v1/account/invoicesInvoices, most recent first: status=unpaid (default), paid or all; pdf_links=true adds to each a link to its PDF, valid 5 minutes.
GET/api/v1/account/ticketsSupport tickets, never their messages: status=open (default) or all.
GET/api/v1/account/auditWhat this application did on the account, newest first, kept 180 days.
GET/api/v1/account/openapi.jsonThe OpenAPI 3.1 description, without signing in.

The actions have their own endpoints: each tool of the tools reference shows its own.

Webhooks

Rather than polling a job, an application can have Ex2 POST to its own HTTPS address when a job it started moves.

EndpointAnswer
GET/api/v1/account/webhooksThis connection’s webhooks, with their last attempt.
POST/api/v1/account/webhooksAdds one: {"url", "events"}. Its secret (whsec_…) comes in this answer only.
DELETE/api/v1/account/webhooks/{id}Deletes one, and its pending deliveries.
Events
job.running, job.done, job.failed, for the jobs the same connection starts after adding the webhook; the body carries the job as get_job shows it.
Signature
Standard Webhooks: webhook-id, webhook-timestamp and webhook-signature headers, the last one v1, followed by the base64 HMAC-SHA256 of id.timestamp.body keyed with the secret. Their libraries check it as is.
Delivery
A 2xx within 10 seconds is a delivery. Otherwise Ex2 tries again after 1 min, 5 min, 30 min, 2 h, 6 h, then gives up. Redirects are not followed.
Rules
HTTPS on a domain name with public addresses only, port 443 or from 1024. At most 5 per connection, one per address, with the scope of an area that starts jobs (WordPress, archives, backups).

Requests and responses

What every call has in common.

Format
JSON over HTTPS, in UTF-8. Request bodies are JSON too (Content-Type: application/json); errors are application/problem+json.
Methods
The catalogue API answers GET, HEAD and OPTIONS only. The account API reads and quotes with GET, acts with POST, and deletes a webhook with DELETE.
Parameters
Ids in the path: {id} is a service or a domain name, as its list gives it. Filters and pages in the query string. An action’s arguments in the JSON body.
Amounts and languages
Numbers, excluding taxes: in the currency asked for in the catalogue (CAD, EUR or USD, named in each answer), in the account’s own currency in the account API. Names, features and links in English or French, as the product pages show them.
CORS
Both APIs are open to any origin, so a browser page can call them; the account API with the Authorization header, never cookies.
Caching
Catalogue prices are read from Ex2’s billing system and answers are public for 10 minutes (5 for a domain check): cache them on your side too. Account answers are private and never cached.
Idempotency
Orders, renewals, plan changes, cancellations, payments, transfers away, tickets and backups need an Idempotency-Key header (a new UUID each time; idempotency_key for the tools). The same key and request get the first answer again for 24 hours, with Idempotent-Replayed: true; the same key with another request is 422; while the first still runs, 409.
Long tasks
WordPress updates and installs, staging copies, archives, backups and restores answer 202 with a job: follow it with GET /api/v1/account/services/{id}/jobs?job=… (the get_job tool), or with a webhook.
Your part
An order, a renewal or a plan change makes an invoice. When the customer has something to do (pay it, add a card, correct their address, turn SSH on, ask support), the answer says what in action_required, with the link.

Pagination

The lists of the account API, and of the account tools, come a page at a time.

Send limit, from 1 to 100 (25 by default). The answer carries next_cursor: send it back as cursor for the next page; it is null on the last one. A page of invoices can hold fewer than limit (drafts are never shown): follow next_cursor all the same.

Every invoice, 50 at a time:

curl "https://api.ex2.com/api/v1/account/invoices?status=all&limit=50" \
  -H "Authorization: Bearer ex2pat_…"
# then, while next_cursor is not null:
curl "https://api.ex2.com/api/v1/account/invoices?status=all&limit=50&cursor=<next_cursor>" \
  -H "Authorization: Bearer ex2pat_…"

Errors

Errors are RFC 9457 problem details: type, title, status, detail, and code, the part for your code. The catalogue API adds the error object it first had, kept for its consumers.

A currency the catalogue does not sell (a live answer):

curl "https://www.ex2.com/api/v1/plans?currency=XYZ"
{
    "type": "urn:ex2:problem:invalid_currency",
    "title": "Invalid parameter",
    "status": 400,
    "detail": "currency must be one of: CAD, EUR, USD.",
    "code": "invalid_currency",
    "error": {
        "code": "invalid_currency",
        "message": "currency must be one of: CAD, EUR, USD."
    }
}
StatuscodeWhen
400invalid_parameter, invalid_currency, invalid_domain, unsupported_tld, invalid_body, idempotency_key_requiredA parameter or the body is not valid, or an action came without its Idempotency-Key.
401unauthorizedNo token, or one that is invalid, expired, revoked or issued for the other resource.
403insufficient_scope, permission_denied, access_lost, outside_limitThe token lacks the scope, the login lacks the client area permission or no longer manages the account (the connection is then closed), or the connection is limited to another service or domain name.
404not_foundNo such endpoint, plan, service, domain name or ticket on the account.
405method_not_allowedA method the endpoint does not take.
409refused, not_allowed, terms_not_accepted, spending_limit, zone_changed, not_bridged, idempotency_in_progress…Not possible now, with the reason: refused by the registrar or the billing system, terms not accepted, over the spending limit, the zone changed since it was read, and others. Often with action_required.
410link_expiredAn invoice’s PDF link after its few minutes: list the invoices again.
422idempotency_key_reusedAn Idempotency-Key already used for another request.
429rate_limitedOver a limit: wait the seconds of Retry-After.
502outcome_unknown, not_appliedThe billing system did not answer a change: check the account before trying again, with a new key.
503whmcs_unavailable, whois_unavailable, server_unavailable, registrar_unavailableThe billing system, a WHOIS server, the hosting server or the registrar did not answer. Try again later.

Each endpoint’s codes are in the OpenAPI descriptions. A change that was accepted but cannot be read back answers 200 with a note, never “nothing was changed”.

Rate limits

Over a limit, the answer is 429 with a Retry-After header, in seconds.

WhatLimit
Domain availability, catalogue API30 per 10 minutes per address
Domain availability through the MCP servers (check_domain)120 per 10 minutes per address
Account API and account tools120 a minute per connection
Invoice PDF downloads30 a minute per connection
Orders, renewals, plan changes, cancellations and transfers away20 an hour per account
Mailbox and forwarder changes30 an hour per account
Database, subdomain, addon domain, alias, cron and PHP changes30 an hour per account
AutoSSL checks started4 a day per service
SSH key changes10 an hour per account
Support tickets opened5 an hour per account
Replies to tickets20 an hour per account
WordPress updates and restores10 an hour per account
WordPress installs5 a day per account
Staging copies made3 a day per account
Staging copies pushed live10 a day per account
Site archives5 a day per account
Archives of a whole hosting account1 a day per service
Restores from backups10 a day per account
Backups on demand2 a day per service

The rest of the catalogue has no set limit: its answers are cached, so ask what you need and cache it too. Whether everything works right now: /api/v1/status.

Versions and stability

APIs
Fields are added, never renamed or removed. A breaking change comes as a new version (/api/v2); the old one keeps answering for at least 12 months, with Deprecation and Sunset headers and a notice here.
MCP servers
Tools keep their names and arguments: new ones are added, none renamed. Each server’s version is in its listing in the MCP registry.

Integrations

No SDK to install: the OpenAPI descriptions generate a client in your language, and the MCP servers plug into AI assistants as they are.

OpenAPI descriptions

Both APIs in OpenAPI 3.1: import them into Postman or Insomnia, a custom GPT’s Actions, or a client generator such as OpenAPI Generator.

MCP registry

Both servers are listed in the official MCP registry, as com.ex2/catalogue and com.ex2/account.

llms.txt

Describes the site and its products for AI agents, and points them to the API and the MCP server.

Agent Skill

Teaches an agent how to use the API and the MCP server, with its index under /.well-known/agent-skills/.

Discovery

The API catalog (RFC 9727), the MCP server card and the ARD manifest, for agents that look for them.

Status

Whether the catalogue API, the MCP servers and the account API work right now, for your monitoring.

Support and feedback

Is it working?

/api/v1/status says whether each part works right now, and which account actions are on.

Something does not work

Open a support ticket with the URL you called, the time, and the answer you got.

A security issue

Write to the address of security.txt, in English or French.

Questions

About the API and the MCP servers.

Do I need an account or an API key?

Not for the catalogue: the API, the public MCP server and llms.txt are open to all. The account server and the account API ask you to sign in with your Ex2 login; for your own scripts, make an API token on the connected assistants page.

Can an assistant order a plan or manage my services through it?

Yes, where you allow it. When you connect it, Ex2’s page lists each kind of action with a box (orders and renewals, domain names, DNS, mail, WordPress and more), and it acts only where you ticked one. An order makes an invoice, which it pays only within the monthly amount you set. Otherwise it reads, and gives you the link to the cart or to the client area.

Is a domain shown as available sure to be mine?

Not quite: the check is a live WHOIS lookup, kept 5 minutes. Someone else can register the name in the meantime, and a premium or reserved name can still be refused at checkout.

Are the prices the ones on the site?

Yes: the same billing system and the same first-year discounts as the product pages. Prices exclude taxes.

Which AI assistants work with the MCP server?

Any client that supports remote MCP servers over Streamable HTTP: Claude, Claude Code, ChatGPT, Cursor, VS Code and others. The public server needs no authentication; the account server uses the sign-in these apps support (OAuth).

Something does not work as described?

Open a support ticket with the URL you called and the answer you got.

Do you have any question?

Contact our support