Domain Expiration API
Overview
To use Domain Expiration, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/domainexpirationExample
How to call the Domain Expiration API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/domainexpiration?domain=myspace.com" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/domainexpiration?domain=myspace.com', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/domainexpiration?domain=myspace.com', headers=headers)
data = response.json()
print(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")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"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
}
}Authentication
The Domain Expiration API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Domain Expiration API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Domain Expiration API:
Check Domain Expiration
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
domain | string | required | The domain to check the expiration date of Format: domain (e.g., myspace.com) | - |
Response
The Domain Expiration API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<domain>myspace.com</domain>
<expirationDate>2029-02-23T05:00:00Z</expirationDate>
<daysToExpiration>1164</daysToExpiration>
<expirationStatus>healthy</expirationStatus>
<createdDate>1996-02-22T05:00:00Z</createdDate>
<lastUpdatedDate>2023-01-17T00:16:21Z</lastUpdatedDate>
<daysSinceLastUpdate>1064</daysSinceLastUpdate>
<domainAgeDays>10890</domainAgeDays>
<domainAgeYears>29.8</domainAgeYears>
</data>
</response>
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
| key | value |
|---|---|
| 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 Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
domain | string | The domain name checked for expiration | |
expirationDatePremium | string | ISO 8601 timestamp of domain expiration date | |
daysToExpiration | number | Number of days until domain expiration | |
expirationStatus | string | Domain health status: expired, critical, warning, healthy | |
createdDatePremium | string | ISO 8601 timestamp when domain was created | |
lastUpdatedDatePremium | string | ISO 8601 timestamp of last domain update | |
daysSinceLastUpdatePremium | number | Number of days since last domain update | |
domainAgeDays | number | Domain age in days (total lifespan) | |
domainAgeYears | number | Domain age in years with decimal precision |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Domain Expiration through GraphQL to combine it with other API calls in a single request. Query only the domain expiration data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
domainexpiration(
input: {
domain: "myspace.com"
}
) {
domain
expirationDate
daysToExpiration
expirationStatus
createdDate
lastUpdatedDate
daysSinceLastUpdate
domainAgeDays
domainAgeYears
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Domain Expiration API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Domain Expiration requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Domain Expiration API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Domain Expiration
Official Domain Expiration packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Domain Expiration works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Domain Expiration?
How many credits does Domain Expiration cost?
Each successful Domain Expiration API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful domain expiration lookups.
Can I use Domain Expiration in production?
The free plan is for testing and development only. For production use of Domain Expiration, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Domain Expiration from a browser?
What happens if I exceed my Domain Expiration credit limit?
When you reach your monthly credit limit, Domain Expiration API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








