Domain Availability Checker is a simple tool for checking the availability of a domain. It returns if the domain is available or not.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Domain Availability response payload
}
}
About the Domain Availability API
Domain Availability Checker works by analyzing the domain provided and checking if it is available. It uses advanced algorithms to check the availability of the domain and returns if the domain is available or not.
What people use it for
- Domain Registration
- Use the Domain Availability Checker API to check domain availability for domain registration. Use the data to find available domains, register new domains, and establish an online presence
- Domain Management
- Check domain availability by using the Domain Availability Checker API for domain management. Use the data to monitor domains, renew registrations, and maintain ownership
- SEO Optimization
- Use the Domain Availability Checker API to check domain availability for SEO optimization. Use the data to find keyword-rich domains, improve rankings, and enhance visibility
- Brand Protection
- Check domain availability by using the Domain Availability Checker API for brand protection. Use the data to secure domains, prevent cybersquatting, and protect brand identity
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
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Domain Availability
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Domain Availability API do?
How do I authenticate Domain Availability API requests?
How much does the Domain Availability API cost?
How fast is the Domain Availability API?
What response formats does the Domain Availability API support?
What HTTP method does the Domain Availability API use?
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
| Parameter | Type | Example | Description |
|---|---|---|---|
domainRequired | string | myspace.com | The domain to check if it is available domain |
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.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
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.
{
"status": "ok",
"error": null,
"data": {
"domain": "myspace.com",
"available": false,
"owner": {
"registrar": "GoDaddy.com, LLC"
}
}
}
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.
| Field | Type | Example | Description |
|---|---|---|---|
domain | string | "myspace.com" | The domain name that was checked for availability |
available | boolean | false | Whether the domain is available for registration |
owner | object | {...} | |
registrarPremium | string | "GoDaddy.com, LLC" | The registrar company managing the domain registration |
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.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
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.
| Plan | Per month | Credits | Domain Availability calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 20 | Free |
| Starter | $29.99 | 200,000 | 20,000 | $1.50 |
| Pro | $99.99 | 1,000,000 | 100,000 | $1.00 |
| Mega | $299.99 | 4,000,000 | 400,000 | $0.75 |
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.
Call it from cURL — GET /v1/domainavailability
No SDK to install — this is a plain HTTPS call to /v1/domainavailability with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/domainavailability" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/domainavailability
Install the Node.js SDK, then call the Domain Availability API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/domainavailabilityconst res = await fetch("https://api.apiverve.com/v1/domainavailability", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/domainavailability
Install the Python SDK, then call the Domain Availability API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-domainavailabilityimport requests
res = requests.get(
"https://api.apiverve.com/v1/domainavailability",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/domainavailability
Install the C# / .NET SDK, then call the Domain Availability API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.DomainAvailabilityusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/domainavailability");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/domainavailability
No SDK to install — this is a plain HTTPS call to /v1/domainavailability with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/domainavailability", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/domainavailability
No SDK to install — this is a plain HTTPS call to /v1/domainavailability with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/domainavailability");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/domainavailability
No SDK to install — this is a plain HTTPS call to /v1/domainavailability with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/domainavailability")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
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.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Domain Availability API.
Domain Data
- BIMI Record Validator
- DKIM Validator
- DMARC Validator
- DNS Lookup
- DNS Propagation Checker
- DNSSEC Checker
- Domain Availability
- Domain Expiration
- Fully Qualified Domain
- MX Lookup
- Reverse DNS Lookup
- SPF Validator
- SSL Certificate Checker
- Subdomain Finder
- URL Lookup
- URL Title
- URL Unshortener
- WHOIS Lookup
Related articles
All articles →
WHOIS Data: Domain Intelligence for Business and SecurityWHOIS data reveals domain ownership, age, and infrastructure. Use it for lead qualification, research, and fraud detection.Read
7 SSL Certificate Problems That Kill TrustExpired certs, mismatched domains, weak encryption. A practical checklist for catching SSL issues before your users do.Read
DNS Lookups: A Developer's Debugging GuideDNS problems cause connection failures and email issues. Learn how to use DNS lookups to diagnose problems faster.Read