Overview
Domain Expiration Checker works by analyzing the domain provided and checking the expiration date. It uses advanced algorithms to check the expiration date of the domain and returns the expiration date.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/domainexpiration?domain=myspace.com" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/domainexpiration?domain=myspace.com', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/domainexpiration?domain=myspace.com",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/domainexpiration?domain=myspace.com", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
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.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
domainRequired | string | The domain to check the expiration date of domain |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"domain": "myspace.com",
"expirationDate": "2029-02-23T05:00:00Z",
"daysToExpiration": 1164,
"expirationStatus": "healthy",
"createdDate": "1996-02-22T05:00:00Z",
"lastUpdatedDate": "2023-01-17T00:16:21Z",
"daysSinceLastUpdate": 1064,
"domainAgeDays": 10890,
"domainAgeYears": 29.8
}
}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 checked for expiration |
expirationDatePremium | string | "2029-02-23T05:00:00Z" | ISO 8601 timestamp of domain expiration date |
daysToExpiration | number | 1164 | Number of days until domain expiration |
expirationStatus | string | "healthy" | Domain health status: expired, critical, warning, healthy |
createdDatePremium | string | "1996-02-22T05:00:00Z" | ISO 8601 timestamp when domain was created |
lastUpdatedDatePremium | string | "2023-01-17T00:16:21Z" | ISO 8601 timestamp of last domain update |
daysSinceLastUpdatePremium | number | 1064 | Number of days since last domain update |
domainAgeDays | number | 10890 | Domain age in days (total lifespan) |
domainAgeYears | number | 29.8 | Domain age in years with decimal precision |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- Domain Management
- Use the Domain Expiration Checker API to check domain expiration for domain management. Use the data to monitor domain registrations, renew domains, and maintain ownership
- SEO Optimization
- Check domain expiration by using the Domain Expiration Checker API for SEO optimization. Use the data to find expiring domains, improve rankings, and enhance visibility
- Brand Protection
- Use the Domain Expiration Checker API to check domain expiration for brand protection. Use the data to secure domains, prevent expiration, and protect brand identity
- Domain Registration
- Check domain expiration by using the Domain Expiration Checker API for domain registration. Use the data to find available domains, register new domains, and establish an online presence
Other ways to use Domain Expiration
Set up Domain Expiration on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Domain Data: