Domain metrics API: Moz, Majestic and Pretty in JSON

Use GET /api2/checkDomain.php when your workflow needs summary domain metrics rather than individual backlink rows. The response combines licensed Moz and Majestic fields with counts from DomDetailer's own Pretty index.

• Moz: mozDA, mozPA, raw mozSpam and link fields.
• Majestic: majesticTF, majesticCF, referring-domain counts and up to three Topical Trust Flow category/value pairs.
• Pretty: observed inbound and outbound links, pages crawled and dofollow link counts.

The complete metric field guide explains interpretation. Keep provider identity and scale with exported figures; authority and flow scores are screening aids, not guaranteed rankings or traffic.

Use HTTPS, keep the key in server-side configuration or an environment variable and identify the caller with app. Send a bare hostname as domain. This Unix-shell example uses a placeholder key; running it with a real key can consume one credit.

curl -G "https://domdetailer.com/api2/checkDomain.php" \
  -H "apikey: YOUR_KEY" \
  --data-urlencode "app=YourResearchTool" \
  --data-urlencode "domain=example.com"

Check authentication first with the free credit balance endpoint. Do not put real keys in browser JavaScript, source control or support screenshots.

Illustrative response excerpt: values below are invented to show the field names, not a live lookup or a complete response.

{
  "domain": "example.com",
  "mozDA": 32,
  "mozPA": 35,
  "mozSpam": 2,
  "majesticTF": 18,
  "majesticCF": 24,
  "majesticRefDomains": 110,
  "prettyLinksIn": 460,
  "prettyPageCount": 60
}

Compute derived values such as TF/CF from the original fields and retain both inputs. Distinguish returned zero from a missing field or failed HTTP request. The documented raw Spam Score scale differs from current Moz percentage displays.

The endpoint takes one domain per request. Deduplicate inputs, start with a small batch, save completed responses and use a bounded queue. Account concurrency is documented up to 20 threads; a sequential example is easier to audit when starting out.

1,000 unique successful requests consume 1,000 credits. That is about $0.79–$1.36 in consumed credit value at the current pack rates. Credits are bought in packs: the entry pack is $34 for 25,000 credits. This is not a $0.79 checkout option. Compare the current DomDetailer credit packs.

For runnable patterns, use the Python CSV guide, PHP cURL guide, Node.js fetch guide or manual Google Sheets batch menu.

Check the HTTP status before interpreting JSON as metrics. Correct invalid inputs or credentials, top up after a 402 response and respect returned retry guidance after a 429. Log status and the domain without recording the API key.

Do not automatically retry every timeout. The server may have completed a charged request even if your client did not receive the response. Keep uncertain rows for investigation and check account usage before repeating them.

forceFresh=1 bypasses the cached Moz record and can take longer; it does not make every source a live crawl. Individual backlinks use the separate backlink data API, and exact-name registry observations use extension coverage.

Use data within the service terms. API access does not grant rights to redistribute provider data or the Pretty dataset.