API changelog and compatibility notes · Language and spreadsheet API examples

Developers

API documentation

Domain metrics, backlink rows and extension coverage, with plain JSON and no SDK required. Each successful data request costs one credit; balance checks are free.

Quick start

Your first request.

Get a key from your account page, put it in the request below, and you have a working integration. There is nothing else to configure.

Checking your balance costs nothing, so it is a safe way to confirm a key works before spending a credit on it.

Confirm the key, then ask for a domain

# Free: does this key work, and what is left on it?
curl -G https://domdetailer.com/api2/checkBalance.php \
  --data-urlencode "apikey=$KEY" \
  --data-urlencode "app=YourApp"
# -> ["UnitsLeft", 92921]

# 1 credit: Moz + Majestic + Pretty for one domain
curl -G https://domdetailer.com/api2/checkDomain.php \
  --data-urlencode "apikey=$KEY" \
  --data-urlencode "app=YourApp" \
  --data-urlencode "domain=example.com"

References

Pick an endpoint.

Domain metrics API

Current

Moz DA and PA, Majestic Trust Flow and Citation Flow, and our own Pretty counts for a single domain. One credit returns the lot.

mozDA majesticTF prettyLinksIn +25 more

Open reference →

Backlinks API

Current

Up to 5,000 individual backlinks with anchor text, source and target URLs and follow status, plus a profile summary.

anchor source nf ref_domains

Open reference →

Extension coverage API

1 credit

Check the same name across all published extensions in one request. Get summary counts and percentage taken, with optional TLD lists. A missing name does not prove registration availability.

taken not_found unknown meta

Open reference →

OpenAPI specification

Tooling

The whole surface as an OpenAPI 3.0 document. Import it into Postman or Insomnia, or generate a typed client from it.

openapi.yaml

Open reference →

Legacy API v1

Deprecated

The original endpoint, kept working for integrations that already use it. Returns fewer fields for the same credit, so there is no reason to choose it for new work.

mozDA majesticTF

Open reference →

At a glance

Every endpoint, and what it costs.

Endpoint	Returns	Credits	Reference
`GET /api2/checkDomain.php`	Moz, Majestic and Pretty metrics for one domain in a single call.	1	Read the checkDomain API reference
`GET /api2/getBacklinks.php`	Up to 5,000 backlink rows for a domain, plus a link profile summary.	1	Read the backlinks API reference
`GET /api2/checkExtensions.php`	Check the same exact name across all published extensions by default. Get counts and percentage taken, with optional taken and not_found lists. Not found does not mean available to register. Each successful request costs one credit total; requests with no usable data are not charged.	1	Read the extension coverage API reference
`GET /api2/checkBalance.php`	How many credits remain on the account. Never charged.	Free	Read the checkBalance API reference

What the numbers mean

Every field defined, with what a good value looks like and which combinations catch a manipulated profile.

Open →

Where the data comes from

How the Pretty index is crawled, parsed and served, and how our definitions differ from other providers.

Open →

Is it up?

Live availability and response times for every endpoint, with recent incident history.

Open →

Questions

Before you integrate.

Which version should I build against?

API v2. It returns everything v1 did plus Pretty metrics and extra Majestic fields, for the same single credit. v1 is maintained only so existing integrations keep working.

Do I need an SDK?

No. The endpoints return plain JSON over HTTP. Any HTTP client will do, and the OpenAPI specification will generate a typed client if you would rather have one.

Does extension coverage tell me whether a domain is available to register?

No. It checks whether the same name appears in downloaded registry datasets across extensions. A registered domain can be absent from a zone file. Read the returned lists and any freshness warnings, and confirm registration availability with a registrar.

API workflows and code examples

Start with the domain metrics API overview or the backlink data API overview, then choose the implementation guide for your workflow.

Read the API changelog and compatibility notes before updating an integration. Check API marketplace listing status for other access routes, or contact DomDetailer about integrating your software.

Start at 25,000 lookups for $34.

One balance covers the browser tools, the desktop app and the API. Nothing renews, nothing expires, and you can stop using it for six months without losing anything.

Buy credits Read the domain metrics API reference