One REST API for your whole stack
Everything you can do in InfraNest, you can automate. Domains, DNS, servers, certificates and monitoring sit behind one endpoint and one token — with signed webhooks and ingest endpoints for the tools you already run.
# List DNS records
curl https://api.infranest.app/v1/dns/records \
-H "Authorization: Bearer inf_live_•••"
{
"data": [
{ "type": "A", "name": "@", "synced": true }
]
}One API for everything InfraNest does
Every product area is available over the same REST API — clean JSON, one token, and the same actions you’d take in the dashboard.
Domains & contacts
Register, transfer, renew and read domains, contacts and expiry across registrars.
GET /v1/domainsDNS
Create, update and sync zones, records and templates — with drift detection.
POST /v1/dns/zones/{id}/recordsServers & cloud
Provision, power-cycle, snapshot and read metrics for servers, volumes and firewalls.
POST /v1/servers/{id}/actionsCertificates
Read your certificate inventory, expiry, posture and coverage gaps.
GET /v1/certificatesMonitoring
Manage checks, read incidents and maintenance, and drive status pages.
GET /v1/monitorsDynamic IP
Manage Dynamic IP sources and the records and firewall rules they drive.
GET /v1/dynamic-ipsTokens with exactly the access you need
Give each API token only the permissions it needs — read or write, per area — with an optional expiry. See when a token was last used, and revoke it any time.
- Read or write access per area — or read-only and full access
- Optional expiry; the token is shown once, then only a hint is kept
- Fair-use rate limits keep everything stable
dns.writedomains.readmonitoring.readcloud.writeinf_live_9f2c•••••••••••••••• · expires in 90d
Webhooks for the events you care about
Point a URL at the events you choose and InfraNest posts to it when they happen — each message signed so you can verify it really came from us. Deliveries are logged, and failures retry automatically.
X-InfraNest-Event: domain.expiring
X-InfraNest-Timestamp: 1720353600
X-InfraNest-Signature: sha256=a1b2c3…
{
"event": "domain.expiring",
"data": { "domain": "example.com", "expires_at": "2026-08-01" }
}Ingest endpoints for the tools you already run
Simple, token-gated endpoints your infrastructure calls in to InfraNest — no login, each with its own scoped token.
Dynamic IP updates
Your router or ddclient reports a changing IP, and your DNS records and firewall rules update automatically.
Heartbeats
A cron job pings a unique URL on a schedule — a missing ping raises an alert.
Deploy hooks
Trigger a deploy from your CI/CD pipeline with a simple inbound webhook — logged with who did it.
Remote probes
Run monitoring checks from your own locations and send the results back securely.
Server agent
A lightweight agent on your servers pushes data in — like a server’s certificates into your inventory.
Safe by design
API & webhook FAQs
How do I verify a webhook is really from InfraNest?
Every webhook is signed with a secret only you and InfraNest share. Each request carries a signature header — recompute it from the request body and your secret, and check the two match. If they do, the message genuinely came from InfraNest and wasn’t changed on the way. Step-by-step examples are in the docs.
Which events can webhooks send?
A domain expiring or changing status, DNS records changing, a server going up or down, a monitoring alert, and the drop-catch lifecycle (a watched domain becoming available or being registered). You choose exactly which events each endpoint receives.
Do I need a paid plan to use the API?
You can start on the free plan. API access and the number of webhook endpoints scale with your plan, so heavier automation lives on the paid tiers.
Is there a rate limit?
Yes — fair-use limits protect the platform and scale with your plan. If you hit one, the API replies with a clear “try again shortly” response, so your script can back off and retry.
Build on InfraNest
Full endpoint reference, authentication and examples live in the interactive API documentation.
Free plan · No credit card required