Validate churn signals API
Actively re-detect churn candidates in real time and get a reasoned verdict per domain. Billed per domain after completion; verdicts cached 48 hours.
Frequently asked questions
When should I use this instead of the confidence score?
When should I use this instead of the confidence score?
What do the four verdicts mean?
What do the four verdicts mean?
confirmed — the technology is absent on a healthy re-detection, so the removal is genuine. false_positive — it is still there, so the churn was a prior crawl miss. masked — a header-detected origin web server is now behind a CDN or proxy, which is a detection change rather than a removal. inconclusive — the site was unreachable, blocked, or gave too little signal.What does it cost?
What does it cost?
inconclusive result is never charged, because that is our side failing rather than yours. Verdicts are cached for 48 hours per domain and technology pair, so a repeat call returns the stored verdict with cached: true at no charge and with no re-crawl. Inconclusive results are never cached, so a retry genuinely re-runs.How many items can I send at once?
How many items can I send at once?
auto or browser mode, and up to 100 in fetch mode. Fetch parallelises at roughly 1–3 seconds per item; browser takes 30–60 seconds each, which is why its cap is small enough to fit a synchronous response. Split larger browser batches on your side.What does auto mode actually do?
What does auto mode actually do?
Authorizations
API key in format tapi_live_[32-char] (live) or tapi_test_[32-char] (test)
Body
The churn candidates to re-check. Maximum 10 items in auto or browser mode, 100 in fetch mode.
1auto routes high-reliability technologies to a fast fetch and everything else straight to a browser, escalating weak fetch results once. fetch parallelises at roughly 1–3 seconds per item. browser takes 30–60 seconds per item.
auto, fetch, browser Click consent banners so consent-gated tags fire.