DomDetailer API changelog

Added task-focused domain metrics, backlink data and extension coverage explanations, metric guides and language examples. Added a Google Sheets workflow that starts paid requests from a confirmed menu action rather than recalculating cells.

These notes describe the website working copy reviewed on this date. Verify the deployed endpoint and response before upgrading an existing integration. The OpenAPI specification and individual reference pages describe the current reviewed contract.

Recorded locally as awaiting upload. Omitting suffixes selects all published datasets. A fixed explicit selection remains available; newly imported datasets join the default selection after publication.

include_taken=1 and include_not_found=1 independently include their lists. Both default to 0. The meta object includes checked, taken, not_found, unknown, percentage_taken and credits_used counts or values. Stale-data warnings use a compact code and count.

Client action: enable both list flags if your client expects the former lists. Supply suffixes if a comparison depends on a fixed set. Calculate coverage using checked datasets, excluding unknown extensions, and preserve any warning.

The release record describes a compact response introduced during testing: domain, name, result lists and meta replaced the earlier per-extension detail format. Routine snapshot details remained internal.

Client action: clients reading the older extensions structure or top-level counters need to adopt the current reference. This historical entry is not the complete current schema; later entries supersede its list defaults and warning shape.

Charging remained one credit per successful request, including partial coverage. Unknown selections are not treated as checked datasets or available names. The release record separately notes live verification of an earlier bundle on this date; that does not establish deployment of every later response change.

1. Compare the current extension coverage reference with the fields your client reads.
2. Make missing optional lists an expected condition rather than a parsing error.
3. Retain meta.checked, meta.unknown and warnings alongside percentages.
4. Use the free balance check to verify authentication.
5. Budget for a real successful test request and confirm the deployed response before a larger batch.

For help with a mismatch, contact DomDetailer support with the date, endpoint, non-secret parameters and response shape. Do not include your API key in a public report.