DNS from your pipeline
The deploy creates the records it needs on its own: the preview subdomain, the verification TXT, the CDN CNAME.
The Unolia REST API exposes the normalized project layer behind scoped tokens, from your code over REST or from your terminal with the unolia CLI. Your scripts stop juggling one credential and one client library per provider.
Work in progress: the DNS endpoints are live today, the rest of the surface opens very soon. We are looking for testers. Become a tester →
The Unolia API gives developers and scripts structured access to the layer Unolia normalizes across providers, over REST or through the unolia command line. Live today: authentication, the current user and token, teams, domains and DNS records, behind personal and team tokens with granular scopes. The rest of the surface, projects, deployments, monitoring, costs and activity, opens to the public as it stabilizes, and what a token may do always follows your plan and your role on the team.
Behind the API sits the same normalization layer as the dashboard: a DNS record has one shape whether the zone lives at Gandi, OVHcloud or Cloudflare. Write the script once, run it on every client, and stop reading provider changelogs.
The point of one normalized API is everything it makes ordinary. The first two run today on the DNS endpoints, the rest follow as the surface opens.
The deploy creates the records it needs on its own: the preview subdomain, the verification TXT, the CDN CNAME.
A 02:00 cron exports every record of every client domain into git. Ten lines of insurance against a very bad day.
Project created, domains attached, monitors set, team invited. Signing a new client becomes a script you run.
At the end of each month, per-project costs flow into your billing tool and the margin per client computes itself.
Uptime, deploys and activity behind your own brand, for your team or your clients. One Laravel route is enough to start.
Every client domain in the same shape, whatever the registrar. The DNS side of the product, scriptable.
/domains
/domains/{domain}
/domains/{domain}/records
/records/{record}
/records/{record}
/teams
/current/token
The whole client file, scriptable.
Deploy from CI, whoever does the hosting.
Watch a site the second it ships.
Every finding Unolia raises, its fix one call away.
Trigger a recipe from anywhere, read the run record back.
Per-project spend, straight into your invoicing.
The agency flight recorder, queryable.
Unolia events pushed into your stack.
The in-progress chapters open with the product, testers see them first
Everything the API exposes, the unolia CLI wraps: same endpoints, same tokens, same scopes. Made for cron jobs, CI steps and the one-liner you run before answering a client.
The CLI ships alongside the public API
Personal tokens act as you, team tokens act as the agency, and both carry granular scopes. Whatever a token claims, the live layer narrows it to what your plan and your current role actually allow, and answers with an honest 402 instead of a surprise.
Read the full reference →Read-only API access with personal tokens.
Write access and team-owned tokens.
Token reach follows each member's live role.
Custom roles shape the same tokens.
Join the waitlist, tell us what you want to script, and get the API before everyone else.
Join the waitlist