MarketXY API
Fresh domain, company, and network intelligence — through one API, JSON responses.
MarketXY's API gives you programmatic access to the same domain registration, WHOIS, DNS, SSL, hosting, technology, company-directory, and network data that powers marketxy.com. Every response is JSON. Every request is authenticated with a single API key. Start with the Universal Query API below, or jump straight to the live API Explorer to try a real request right now.
Authentication
Every request requires an API key, passed as either an X-API-Key header or a
Bearer token in Authorization — pick whichever your HTTP client supports.
curl "https://api.marketxy.com/v4/query?type=domain&value=yahoo.com" \
-H "X-API-Key: mxy_live_your_key_here"
curl "https://api.marketxy.com/v4/query?type=domain&value=yahoo.com" \
-H "Authorization: Bearer mxy_live_your_key_here"
Base URL & environments
| Environment | Base URL | Notes |
|---|---|---|
| Production | https://api.marketxy.com | Real data, real billing, real rate limits. |
Rate limits & plans
Every request spends MarketXY Data Tokens from your plan. Data Tokens measure the amount and type of data a request returns — they are not AI/LLM tokens, cryptocurrency or credits — so a request that returns more data costs more. Each plan also has a daily and an hourly token budget and a per-second burst limit.
| Plan | Price | Data Tokens / month | Requests / month | Requests / day | Requests / hour | Requests / second |
|---|---|---|---|---|---|---|
| Free | $0 | 1,000,000 | 5,000 | 500 | 500 | 1 |
| Startup | $19 | 15,000,000 | 10,000 | 1,000 | 1,000 | 2 |
| Enterprise | $99 | 100,000,000 | 100,000 | 10,000 | 10,000 | 5 |
These are the plans and numbers on the pricing page. Check your tokens, your daily and hourly budget and your burst limit anytime with GET /v4/api-plan/status — see Self-discovery endpoints.
Errors
The Universal Query API uses one consistent error shape:
{
"success": false,
"request_id": "req_0d42353593c8f850",
"error": {
"code": "UNKNOWN_INCLUDE_SECTION",
"message": "Unknown section(s) in \"include\": company. Valid: whois, dns, ssl, hosting, technologies, social, scores, counts, misc, or \"all\"."
}
}
Authentication errors (401) carry the same fields plus the older statusCode and message, kept for existing integrations:
{
"statusCode": 401,
"message": "Missing API key. Pass it as an 'X-API-Key' header (or 'Authorization: Bearer <key>').",
"success": false,
"request_id": "req_...",
"error": {
"code": "MISSING_API_KEY",
"message": "Missing API key. Pass it as an 'X-API-Key' header (or 'Authorization: Bearer <key>')."
}
}
| Status | code | Meaning |
|---|---|---|
| 400 / 422 | MISSING_DATA_POINT, UNKNOWN_DATA_POINT, UNKNOWN_FIELD, UNKNOWN_INCLUDE_SECTION, COUNT_NOT_SUPPORTED | Bad request — message names the exact problem. |
| 401 | MISSING_API_KEY, INVALID_API_KEY | Missing or invalid/revoked API key. The body also keeps the older statusCode and message fields. |
| 402 | — | Free trial expired. |
| 403 | REMOVED | This record has been removed and can no longer be shown. |
| 404 | NOT_FOUND | No record for this exact-lookup value. |
| 429 | — | Data Token budget or burst limit exceeded (scope field tells you which). Burst errors include a retry_after (seconds) and a matching Retry-After header. |
| 500 | INTERNAL_ERROR | Server-side error. Safe to retry. |
| 503 | COUNT_TEMPORARILY_UNAVAILABLE, QUERY_TEMPORARILY_UNAVAILABLE | A dependency was temporarily slow. Includes a retry_after (seconds) — safe to retry after that. |
Pagination
- Cursor-based (registrar, nameserver, tld, country, ip, cms, web_server, technology, mx, create_date, update_date, expiry_date): pass
limit(default 100, max 1000) and the previous response'snext_cursorascursor. companyuses the samelimit+cursorparameters (limitdefault 20, max 100): pass the previous response'snext_cursorascursorto get the next page of matches.page/pageSizeare not read by/v4/query.- Page-based (most Additional Data APIs): pass
pageandpageSize/limit.
Universal Query API
One endpoint, one shape, sixteen data points.
GET /v4/query is the fastest way to look up domain, company, email, ASN, or reverse/date-range data — pick a type, give a value, get JSON back.
curl "https://api.marketxy.com/v4/query?type=domain&value=yahoo.com&include=whois,ssl" \
-H "Authorization: Bearer mxy_live_your_key_here"
type vs data_pointBoth work identically — type is the newer, friendlier name; data_point still works unchanged for existing integrations.API Explorer
Build a real request below and send it — this calls the live production API directly from your browser.
All 16 data points
| type | kind | Description | Example |
|---|---|---|---|
domain | exact | Everything MarketXY has on one domain | ?type=domain&value=yahoo.com |
email | exact | Person/company record by exact email, plus its domain | [email protected] |
asn | exact | ASN registry info (name, org, IP ranges) | ?type=asn&value=AS15169 |
company | search | Fuzzy search the company directory by name/website/phone | ?type=company&value=Microsoft |
create_date | reverse | Domains created on a given day | ?type=create_date&value=2026-09-09 |
update_date | reverse | Domains updated on a given day | ?type=update_date&value=2026-09-09 |
expiry_date | reverse | Domains expiring on a given day | ?type=expiry_date&value=2026-09-09 |
registrar | reverse | Domains registered through a given registrar | ?type=registrar&value=GoDaddy |
nameserver | reverse | Domains using a given name server | ?type=nameserver&value=ns1.example.com |
mx | reverse | Domains using a given MX record | ?type=mx&value=mail.example.com |
tld | reverse | Domains under a given TLD | ?type=tld&value=com |
country | reverse | Domains whose WHOIS registrant country matches | ?type=country&value=US |
ip | reverse | Domains hosted on a given IPv4 address | ?type=ip&value=8.8.8.8 |
cms | reverse | Domains using a given CMS | ?type=cms&value=WordPress |
web_server | reverse | Domains running a given web server | ?type=web_server&value=nginx |
technology | reverse | Domains using a given technology (substring match) | ?type=technology&value=React |
Include sections (domain only)
| Section | Covers |
|---|---|
whois | Registrant, registrar, create/update/expiry dates |
dns | Nameservers, A/MX/TXT records |
ssl | Certificate issuer, subject, expiry, subject and issuer country |
hosting | IPv4 / IPv6 address (for ASN data use ?type=asn) |
technologies | CMS, web server, detected tech stack |
social | Linked social profiles |
scores | MXY rank / overall score fields |
counts | Subdomain count, related-domain counts |
misc | Robots.txt, on-page emails/phones (masked), page meta, main country and the country-by-IP / language / meta tag / ccTLD signals |
Country signals (domain)
One type=domain request returns every country signal MarketXY holds for a domain. Each signal comes from a different source, so they can disagree — for example a site hosted on a US CDN but registered and certified in the UK.
| Field | Section | What it tells you | Example (bbc.co.uk) |
|---|---|---|---|
main_country | misc | MarketXY’s best single answer for the domain’s country (computed; not the same as the registrant country) | GB |
registrant_country | whois | Country in the WHOIS registrant record. Often empty when WHOIS privacy is on | "" |
country_by_ip | misc | Country of the server’s IP address (hosting location; a CDN shows the CDN’s country) | US |
country_by_cctld | misc | Country implied by the domain ending, e.g. .uk | uk |
country_by_lang | misc | Country implied by the website’s language | GB |
country_by_meta | misc | Country found in the page’s meta tags | US |
ssl_subject_country | ssl | Country of the organisation the certificate was issued to | GB |
ssl_issuer_country | ssl | Country of the certificate authority that signed it — not the website’s country | BE |
Use include=whois,ssl,misc to get whole sections, or fields= to get only the fields you name. When fields is given it is used instead of include. An unknown name returns UNKNOWN_FIELD; the valid names are listed by GET /v4/data-points/domain.
curl "https://api.marketxy.com/v4/query?type=domain&value=bbc.co.uk&fields=main_country,registrant_country,country_by_ip,country_by_cctld,country_by_lang,country_by_meta,ssl_subject_country,ssl_issuer_country" \
-H "X-API-Key: mxy_live_your_key_here"
{
"success": true,
"request_id": "req_...",
"data": {
"query": { "data_point": "domain", "value": "bbc.co.uk" },
"result": {
"domain": "bbc.co.uk",
"main_country": "GB",
"registrant_country": "",
"country_by_ip": "US",
"country_by_cctld": "uk",
"country_by_lang": "GB",
"country_by_meta": "US",
"ssl_subject_country": "GB",
"ssl_issuer_country": "BE"
}
},
"meta": { "data_point": "domain", "match_type": "exact" }
}
"" or null. When you need one answer, use main_country.Count mode
Add count=true to any reverse or search data point for a real match count with no rows fetched.
{
"success": true,
"request_id": "req_b02c25ca454bac37",
"data": { "query": { "type": "tld", "value": "com" }, "matched_count": 136703797 },
"meta": { "data_point": "tld", "match_type": "reverse", "count_only": true }
}
count=true on domain, email, or asn returns COUNT_NOT_SUPPORTED.Response envelope
{ "success": true, "request_id": "req_...", "data": { ... }, "meta": { ... } }
{ "success": false, "request_id": "req_...", "error": { "code": "...", "message": "..." } }
Additional Data APIs
Beyond the Universal Query API, MarketXY exposes ~45 specialized routers under /v4/* — each authenticated and rate-limited the same way as /v4/query.
Company data
| Base path | Purpose | Status |
|---|---|---|
/v4/company | Company lookup/search (older router) | Stable |
/v4/company2026 | Newer, larger dataset (272 collections, ~51M docs) | Stable |
/v4/company-database | Global company directory — search by name/website/phone/country | Stable |
/v4/company-registry | Per-country structured registries (Brazil CNPJ, India CIN, Canada, Australia ACN, US, and more) | Stable |
/v4/company-research | Deeper company research/profile data | Beta |
/v4/company-enrichment | Cross-references WHOIS + person registry by ?domain= and/or ?phone= — real WHOIS contact plus related contacts/domains for the company. | Stable |
/v4/domain-companies | Companies in the global directory whose own website is one domain, or a subdomain of it. GET ?domain=example.com | Stable |
/v4/lead-generation | Lead-generation queries over company/contact data | Beta |
Domain Companies — GET /v4/domain-companies
A domain-filtered view of the global company directory (the same company_* index and the same "website is this domain or a subdomain of it" match /v4/company-database and the product's own "Related Companies" card already use) — one real call instead of a generic search the client has to post-filter itself.
| Param | Required | Notes |
|---|---|---|
domain | Yes | A bare domain, e.g. example.com. |
pageSize | No | Max rows to check, max 100 (default 50). |
curl "https://api.marketxy.com/v4/domain-companies?domain=example.com" \
-H "X-API-Key: mxy_live_your_key_here"
import requests
resp = requests.get(
"https://api.marketxy.com/v4/domain-companies",
params={"domain": "example.com"},
headers={"X-API-Key": "mxy_live_your_key_here"},
)
print(resp.json())
$ch = curl_init("https://api.marketxy.com/v4/domain-companies?domain=example.com");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["X-API-Key: mxy_live_your_key_here"]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
curl_close($ch);
echo $response;
const res = await fetch("https://api.marketxy.com/v4/domain-companies?domain=example.com", {
headers: { "X-API-Key": "mxy_live_your_key_here" },
});
console.log(await res.json());
{
"statusCode": 200,
"data": {
"domain": "example.com",
"total": 1,
"companies": [
{ "company": "Example Inc.", "website": "example.com", "relation": "exact", "category": "...", "city": "...", "country": "..." }
]
}
}
relation is exact (the company's own website is this exact domain) or subdomain (its website is a subdomain of it) — never a loose text match.
Domain intelligence
| Base path | Purpose | Status |
|---|---|---|
/v4/ (domain routes) | Core domain profile endpoints (predates Universal Query) | Stable |
/v4/domain-life-cycle | Domain lifecycle stage — registration date, expiry, redirect/blank-page status, government/educational/test TLD, blacklist status. GET ?domain=example.com | Stable |
/v4/domain-score/{domain} | Domain quality/trust score (path param, not ?domain=). Coverage is partial — many well-known domains have no score computed yet. | Stable |
/v4/overall-score | Composite overall domain score | Beta |
/v4/domain-category/{domain} | Domain's real business category (path param, not ?domain=), with rank within that category. Coverage is partial — many domains have no category assigned yet. | Stable |
/v4/domain-rating, /domain-rating-criteria, /domain-relation-rating, /category-rating | Domain/category rating system | Beta |
/v4/category | Category directory | Beta |
/v4/domain-validity | Classifies a raw input string as a domain, subdomain, email address, unknown-TLD value, or invalid format, with the real reason. GET ?value= | Stable |
Domain Validity — GET /v4/domain-validity
Classifies a raw input string: a real domain, a subdomain of one, something that looks like an email address, a domain with an unknown/invalid TLD, or a plain invalid format — with the real reason, never a guess. "Known TLD" is checked against the same live TLD directory /v4/tlds uses, not a hand-maintained list.
| Param | Required | Notes |
|---|---|---|
value | Yes | The value to classify — a domain, subdomain, or email address. |
curl "https://api.marketxy.com/v4/domain-validity?value=abc%40gmail.con" \
-H "X-API-Key: mxy_live_your_key_here"
import requests
resp = requests.get(
"https://api.marketxy.com/v4/domain-validity",
params={"value": "[email protected]"},
headers={"X-API-Key": "mxy_live_your_key_here"},
)
print(resp.json())
$ch = curl_init("https://api.marketxy.com/v4/domain-validity?" . http_build_query(["value" => "[email protected]"]));
curl_setopt($ch, CURLOPT_HTTPHEADER, ["X-API-Key: mxy_live_your_key_here"]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
curl_close($ch);
echo $response;
const res = await fetch("https://api.marketxy.com/v4/domain-validity?" + new URLSearchParams({ value: "[email protected]" }), {
headers: { "X-API-Key": "mxy_live_your_key_here" },
});
console.log(await res.json());
{
"statusCode": 200,
"data": {
"input": "[email protected]",
"type": "email_address",
"reason": "Contains \"@\" - this is an email address, not a domain.",
"emailDomain": "gmail.con",
"emailDomainIssue": { "type": "unknown_tld", "reason": "\".con\" is not a known top-level domain (did you mean a common TLD like .com, .net, .org?)" }
}
}
Network & infrastructure
| Base path | Purpose | Status |
|---|---|---|
/v4/asn | ASN/network registry lookups (legacy — prefer type=asn) | Deprecated |
/v4/hosting-providers | Hosting-provider market-share stats (legacy) | Deprecated |
/v4/hosting-market-share | Real hosting-provider market share, computed from a 493,658-domain sample resolved against real IP-range/ASN data. | Stable |
/v4/geoip | IP-to-geolocation lookups | Beta |
/v4/ipdb-registry | IP address database / registry | Beta |
/v4/dns | DNS record lookups (legacy router) | Stable |
/v4/ssl-database/:field | SSL certificate database — search one field (e.g. subjectOrganization, subjectCountry) with ?search=; the bare path answers 400 with the sub-routes | Stable |
WHOIS & registry
| Base path | Purpose | Status |
|---|---|---|
/v4/whois | Raw WHOIS record lookups (legacy router) | Stable |
/v4/actes | Direct access to the underlying actes2025 dataset | Stable |
/v4/tlds | TLD directory/stats | Stable |
/v4/registrars | Registrar directory/stats | Stable |
/v4/whois-summary | Lean WHOIS lookup — create/update/expiry date, registrar, registrant country, registrant name and registrant company, in one call. GET ?domain=example.com | Stable |
WHOIS Summary — GET /v4/whois-summary
The WHOIS registrant/date fields for one domain, in one lean call, instead of the full Universal Query envelope. registrantName and registrantCompany are returned raw/unmasked here — unlike the Universal Query API's own flat-field dictionary, which only returns registrant_country for privacy reasons.
| Param | Required | Notes |
|---|---|---|
domain | Yes | A bare domain, e.g. example.com. |
field | No | Return only one field instead of the full object. One of: createDate, updateDate, expiryDate, registrar, registrantCountry, owner (registrant name), company (registrant company). An unrecognized value returns a 400 listing the valid names. |
curl "https://api.marketxy.com/v4/whois-summary?domain=example.com" \
-H "X-API-Key: mxy_live_your_key_here"
import requests
resp = requests.get(
"https://api.marketxy.com/v4/whois-summary",
params={"domain": "example.com"},
headers={"X-API-Key": "mxy_live_your_key_here"},
)
print(resp.json())
$ch = curl_init("https://api.marketxy.com/v4/whois-summary?domain=example.com");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["X-API-Key: mxy_live_your_key_here"]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
curl_close($ch);
echo $response;
const res = await fetch("https://api.marketxy.com/v4/whois-summary?domain=example.com", {
headers: { "X-API-Key": "mxy_live_your_key_here" },
});
console.log(await res.json());
{
"statusCode": 200,
"data": {
"domain": "shopify.com",
"found": true,
"createDate": "2005-03-11",
"updateDate": "2025-09-02",
"expiryDate": "2027-03-11",
"registrar": null,
"registrantCountry": "CA",
"registrantName": null,
"registrantCompany": "Shopify Inc."
}
}
Any field is null, never a guess, when we have no WHOIS record or that specific field is empty on it — registrar/registrantName above are real gaps for shopify.com specifically, not a bug.
Only one field — add &field= to get back just that field (e.g. for a billing dashboard that only ever shows the expiry date):
curl "https://api.marketxy.com/v4/whois-summary?domain=shopify.com&field=expiryDate" \
-H "X-API-Key: mxy_live_your_key_here"
{
"statusCode": 200,
"data": {
"domain": "shopify.com",
"found": true,
"expiryDate": "2027-03-11"
}
}
Security & threat data
| Base path | Purpose | Status |
|---|---|---|
/v4/phishing-alerts | Phishing-style look-alikes for one brand domain (brand name + a phishing keyword in the same domain name). GET ?domain=example.com | Stable |
/v4/typosquat-domains | Typosquatting domain detection — real registered look-alikes of a brand domain, with first-found date and severity. GET ?domain=example.com | Stable |
/v4/blacklisted/malware | Is this domain (or its own flagged subdomains) carrying the real Malware blacklist category? GET ?domain=example.com | Stable |
/v4/blacklisted/fraud | Is this domain (or its own flagged subdomains) carrying the real Fraud blacklist category? GET ?domain=example.com | Stable |
/v4/blacklisted | Blacklisted-domains database | Stable |
/v4/email-domain-type/check | Is a domain disposable, a free email provider, or a company domain? GET ?domain=example.com | Stable |
/v4/signup-protection/check | Combined signup-fraud check for a signup form — disposable/free/company email, real-time blacklist status, domain trust score and domain age, plus one risk verdict. GET ?email= or ?domain= | Stable |
/v4/block-list | Block-list management/lookup | Beta |
Full request/response detail for the Stable security endpoints — the other rows above are Beta and not yet documented per-parameter. A browsable landing page for domain classification is also at /email-domain-type/, and for signup protection at /signup-protection-api/.
Email Domain Type — GET /v4/email-domain-type/check
Classifies one domain as disposable, free (a consumer provider like Gmail/Yahoo/Outlook), or company (a real business domain) — plus a separate hostingProvider signal (Google Workspace / Microsoft 365 / Zoho Mail) that never reclassifies a real company as "free" just because a consumer platform hosts its mail. type is null, never a guess, when we have no classification for a domain.
| Param | Required | Notes |
|---|---|---|
domain | Yes | A bare domain, e.g. example.com (no scheme/path). |
curl "https://api.marketxy.com/v4/email-domain-type/check?domain=example.com" \
-H "X-API-Key: mxy_live_your_key_here"
import requests
resp = requests.get(
"https://api.marketxy.com/v4/email-domain-type/check",
params={"domain": "example.com"},
headers={"X-API-Key": "mxy_live_your_key_here"},
)
print(resp.json())
$ch = curl_init("https://api.marketxy.com/v4/email-domain-type/check?domain=example.com");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["X-API-Key: mxy_live_your_key_here"]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
curl_close($ch);
echo $response;
const res = await fetch("https://api.marketxy.com/v4/email-domain-type/check?domain=example.com", {
headers: { "X-API-Key": "mxy_live_your_key_here" },
});
console.log(await res.json());
{
"statusCode": 200,
"data": {
"domain": "yoocco.com",
"type": "company",
"source": "actes-z7",
"hostingProvider": "google-workspace",
"found": true
}
}
source is actes-z7 for a real crawled classification, or curated-list (major free providers — Gmail, Yahoo, Outlook/Hotmail, iCloud, AOL, ProtonMail, Zoho, GMX, Yandex, Mail.ru) / disposable-email-domains-package (a 121,570-domain open-source list) when the crawl has nothing and a maintained fallback list answers instead — the fallback never overrides a real crawled classification.
Blacklisted Domain Explorer — GET /v4/blacklisted/explorer
Searches MarketXY's real flagged-domain/subdomain/IP database.
| Param | Required | Notes |
|---|---|---|
search | No | Free-text filter. |
recordType | No | Restrict to one record kind. |
page, pageSize | No | pageSize max 100, default 25. |
sortField, sortType | No | Default domain / asc. |
filters | No | A JSON object, URL-encoded. |
curl "https://api.marketxy.com/v4/blacklisted/explorer?pageSize=10" \
-H "X-API-Key: mxy_live_your_key_here"
import requests
resp = requests.get(
"https://api.marketxy.com/v4/blacklisted/explorer",
params={"pageSize": 10},
headers={"X-API-Key": "mxy_live_your_key_here"},
)
print(resp.json())
$ch = curl_init("https://api.marketxy.com/v4/blacklisted/explorer?pageSize=10");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["X-API-Key: mxy_live_your_key_here"]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
curl_close($ch);
echo $response;
const res = await fetch("https://api.marketxy.com/v4/blacklisted/explorer?pageSize=10", {
headers: { "X-API-Key": "mxy_live_your_key_here" },
});
console.log(await res.json());
{
"statusCode": 200,
"data": {
"hits": [
{
"_source": {
"domain": "000717-coinbase.com",
"parent_domain": null,
"d_or_subd": 1,
"i7": "Malicious",
"h2": "2025-05-29",
"h1": "2026-10-11",
"h0": "2025-05-29",
"z8": ["raw.githubusercontent.com", "phishing-database-active", "dangerous-domains", "src262"]
}
}
]
}
}
domain/parent_domain/d_or_subd (0=subdomain, 1=domain, 2=IP) identify what's flagged; i7 is the category (Phishing/Malware/Malicious/Fraud/Adult/Threat/Toxic); h2 is first-found, h1 last-rechecked, h0 last-update; z8 lists the threat feed(s) that flagged it. The remaining _source fields are internal ES codes shared with other datasets — a full per-field reference for this endpoint is on the roadmap, not yet published.Signup Protection — GET /v4/signup-protection/check
One real-time call for a signup form: email type (disposable / free / company), exact blacklist status, domain trust score and domain age, combined into one risk/recommendation/reasons verdict — instead of calling 4 separate endpoints and combining the logic yourself.
| Param | Required | Notes |
|---|---|---|
email | One of email/domain | A full email address, e.g. [email protected] (its domain is checked). |
domain | One of email/domain | A bare domain to check directly. |
curl "https://api.marketxy.com/v4/signup-protection/check?email=user%40example.com" \
-H "X-API-Key: mxy_live_your_key_here"
import requests
resp = requests.get(
"https://api.marketxy.com/v4/signup-protection/check",
params={"email": "[email protected]"},
headers={"X-API-Key": "mxy_live_your_key_here"},
)
print(resp.json())
$ch = curl_init("https://api.marketxy.com/v4/signup-protection/check?" . http_build_query(["email" => "[email protected]"]));
curl_setopt($ch, CURLOPT_HTTPHEADER, ["X-API-Key: mxy_live_your_key_here"]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
curl_close($ch);
echo $response;
const res = await fetch("https://api.marketxy.com/v4/signup-protection/check?" + new URLSearchParams({ email: "[email protected]" }), {
headers: { "X-API-Key": "mxy_live_your_key_here" },
});
console.log(await res.json());
{
"statusCode": 200,
"data": {
"input": "000717-coinbase.com",
"domain": "000717-coinbase.com",
"email": { "type": null, "source": null, "hostingProvider": null, "found": false },
"blacklist": { "exactMatch": true, "hits": 1, "subdomainFlaggedTotal": 0 },
"riskScore": null,
"domainAge": { "found": true, "createDate": "2025-05-29", "ageDays": 520 },
"verdict": { "risk": "high", "recommendation": "block", "reasons": ["Domain is on the real-time blacklist."] }
}
}
A browsable version of this with real worldwide stats is at /signup-protection-api/.
People & contacts
| Base path | Purpose | Status |
|---|---|---|
/v4/person-registry/list | Global contact registry (~1.09B records), searched with ?search= — also powers type=email; the bare path answers 400 with the sub-routes | Stable |
/v4/domain-contacts | Contacts on file for one domain, from the global person registry. GET ?domain=example.com | Stable |
/v4/email | Found-email database (legacy router) | Deprecated |
Domain Contacts — GET /v4/domain-contacts
A domain-filtered view of /v4/person-registry/list — the real contacts on file for one domain, in one call. Email/phone are masked, the same as the person registry itself; each row's id/phoneId can be exchanged for the real value at /v4/person-registry/email-reveal/:token//phone-reveal/:token (rate-limited, one free reveal per IP per hour).
| Param | Required | Notes |
|---|---|---|
domain | Yes | A bare domain, e.g. example.com. |
page | No | Page number, default 1. |
pageSize | No | Rows per page, max 100, default 20. |
curl "https://api.marketxy.com/v4/domain-contacts?domain=example.com" \
-H "X-API-Key: mxy_live_your_key_here"
import requests
resp = requests.get(
"https://api.marketxy.com/v4/domain-contacts",
params={"domain": "example.com"},
headers={"X-API-Key": "mxy_live_your_key_here"},
timeout=45,
)
print(resp.json())
$ch = curl_init("https://api.marketxy.com/v4/domain-contacts?domain=example.com");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["X-API-Key: mxy_live_your_key_here"]);
curl_setopt($ch, CURLOPT_TIMEOUT, 45);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
curl_close($ch);
echo $response;
const res = await fetch("https://api.marketxy.com/v4/domain-contacts?domain=example.com", {
headers: { "X-API-Key": "mxy_live_your_key_here" },
});
console.log(await res.json());
{
"statusCode": 200,
"data": {
"domain": "shopify.com",
"total": 44,
"page": 1,
"pageSize": 20,
"data": [
{ "id": "token...", "email": "j***@shopify.com", "phone": "+1512***51", "phoneId": "token...", "country": "US", "extraCount": 0, "extraContacts": [] }
]
}
}
Misc & account
| Base path | Purpose | Status |
|---|---|---|
/v4/social-media | Linked social-media profile data | Beta |
/v4/technology-database | Technology/tech-stack directory (lookup by technology name, e.g. wordpress) | Beta |
/v4/domain/{domain}/technologies | Technology stack for one domain — CMS, web server, CSS framework, analytics, and more. GET (path param, not ?domain=) | Stable |
/v4/country-meta | Country metadata reference | Beta |
/v4/count | Internal cached-stats counters (see count mode instead) | Stable |
/v4/lookup | Unified lookup by domain/email/phone (older pattern) | Stable |
/v4/api-plan | Your key's status/usage | Stable |
/v4/categories | Category CRUD — account management, not a data query | Stable |
/v4/omni-search | Free-text search across multiple data types at once | Stable |
/v4/client-domains, /client/asn, /client-whois, /client-domain-life-cycle, /client | Account-scoped ("my saved domains") variants | Beta |
Self-discovery endpoints
| Endpoint | Returns |
|---|---|
GET /v4/ | API root — name, version, status, links |
GET /v4/data-points | All 16 data points (name, aliases, kind, description, example) |
GET /v4/data-points/:name | Deep detail — includable sections and every real field name |
GET /v4/api-plan/status | Your key's current plan, usage, remaining quota |
GET /v4/api-plan/key | Your key's metadata — never the raw key after first creation |
Roadmap & known limitations
- Full parameter reference for the Additional Data APIs — currently indexed by name and purpose; a complete per-endpoint reference (parameters, types, examples in multiple languages) is on the roadmap. Until then, the Universal Query API is the most fully-documented and recommended way to access this data.
- Legacy ASN/hosting-provider endpoints (
/v4/asn,/v4/hosting-providers) — deprecated legacy routes; they still answer today but may be removed. Usetype=asnon the Universal Query API instead. - Legacy email-database endpoint (
/v4/email) — deprecated legacy route; it still answers today but may be removed. Usetype=emailon the Universal Query API instead. - Some lookups may occasionally take longer under heavy load — these return a clear
503with aretry_afterhint rather than hanging; simply retry. - Company results are not yet linked directly to a domain's profile — use the separate
type=companysearch for now; a direct link is planned.
Changelog
| Date | Change |
|---|---|
| 2026-10-31 | Added an optional field= param to /v4/whois-summary to return just one field (create/update/expiry date, registrar, registrant country, owner, or company) instead of the full object. |
| 2026-10-30 | Added /v4/signup-protection/check, /v4/whois-summary, /v4/domain-contacts, /v4/domain-companies and /v4/domain-validity. |
| 2026-09-29 | Added type= alias for data_point= and real count=true mode. |
| 2026-09-29 | Fixed type=email hanging then 500ing under cluster load — now a fast, honest timeout. |
| 2026-09-22 | Universal Query API launched — 16 data points, one response shape. |
Documentation generated from the MarketXY API codebase and validated against currently supported endpoints. Last updated 2026-10-30.