Void API — your domains, over REST.
Check availability, register and renew, switch nameservers, put a domain behind Cloudflare and manage its DNS, security switches and redirects — from your own code, on the same account and balance as the bot.
Objects & statuses
Domain
{
"id": "0a797218-8ec5-45d5-aa23-cb85c28a7d3b",
"domainName": "example.org",
"status": "ACTIVE", // PENDING · ACTIVE · EXPIRED · FAILED
"nameservers": ["ns1.voidhosting.org", "ns2.voidhosting.org"],
"price": "16.00", // paid for the current term
"renewalPrice": "16.00", "renewalYears": 1,
"autoRenew": false,
"expiresAt": "2027-08-28T17:04:38.000Z",
"createdAt": "2026-08-28T17:04:40.113Z",
"blockFlags": [] // "google" · "metamask" · "registrar"
}Domain status
PENDING | registration in flight (seconds) |
ACTIVE | yours, resolving |
EXPIRED | past expiry; renewable for 30 days |
FAILED | registry refused; refunded |
Zone status
none | not connected |
pending | waiting for the nameserver switch |
active | Cloudflare is serving the zone |
moved | nameservers point elsewhere — reconnect or disconnect |
Notifications
Events that concern a domain — registration, renewal (manual or automatic), expiry reminders at 7/3/1 days, blocklist hits — are delivered to the account in the Telegram bot regardless of which client caused them, and to your webhooks if you registered any.
Scope & changes
v1 covers domains. Servers and web hosting will join under the same keys and conventions (/v1/servers, /v1/hostings); nothing documented here changes shape when they do. Additive changes (new fields, new endpoints) happen without notice; anything breaking ships as /v2 with v1 kept alive.
Machine-readable description: openapi.json (OpenAPI 3.0). Questions and bugs — @voidsup.