Domain Availability API

About the Domain Availability API

Domain Availability is a domain check API: pass one domain name and it reports whether the domain is available to register, plus its creation and expiry dates when it is already taken. It queries the registry over RDAP, falling back to WHOIS, at the time of the request. Paid plans also get the TLD's registration, renewal and transfer price range across registrars, refreshed weekly, and a flag for names the registry likely prices as premium.

What people use it for

Business Name Generators

When entrepreneurs test company names, business formation apps verify if matching dot-com addresses are unregistered before finalizing entity paperwork.

Domain Reseller Storefronts

Show buyers instant availability flags and registration expiry dates directly inside custom search bars for registrar and web hosting portals.

Trademark Defense Audits

Legal teams scan potential brand collisions across key top-level domains, inspecting registration dates to establish prior use or bad-faith squatting.

Agency Rebranding Workflows

Filter out claimed domains early during client naming sprints so design studios pitch only project handles that can actually be acquired.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON

Default REST response

XML

Markup format

YAML

Human-readable

CSV

Tabular export

Beta

GraphQL

Query language

New

MCP

For AI agents

How it compares

Side by side with the tools people weigh Domain Availability against — what each one is better at, in plain terms.

Request parameters — GET /v1/domainavailability

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

1
2

curl "https://api.apiverve.com/v1/domainavailability?domain=myspace.com" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Response — GET /v1/domainavailability

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

{
  "status": "ok",
  "error": null,
  "data": {
    "domain": "myspace.com",
    "available": false,
    "owner": {
      "registrar": "GoDaddy.com, LLC",
      "createdDate": "1996-02-22T05:00:00Z",
      "expiryDate": "2029-02-23T05:00:00Z"
    },
    "source": "rdap",
    "pricing": {
      "tld": "com",
      "currency": "USD",
      "registration": {
        "low": 11.08,
        "high": 11.25
      },
      "renewal": {
        "low": 11.08,
        "high": 11.25
      },
      "transfer": {
        "low": 11.08,
        "high": 11.25
      },
      "sources": 2,
      "premiumLikely": null,
      "premiumReason": null,
      "updatedAt": "2026-10-18T10:00:00.000Z"
    },
    "lifecycle": "registered",
    "eppStatus": [
      "client delete prohibited",
      "client renew prohibited",
      "client transfer prohibited",
      "client update prohibited"
    ],
    "nameservers": [
      "ns-cloud-a1.googledomains.com",
      "ns-cloud-a2.googledomains.com",
      "ns-cloud-a3.googledomains.com",
      "ns-cloud-a4.googledomains.com"
    ],
    "isParked": false,
    "isForSale": false,
    "parkingService": null
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

What a call costs — 10 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Zero-code embed — one snippet, no backend

Drop an interactive Domain Availability form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — Domain Availability API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1Data refreshed realtime