Customer API
Put ransomware leak-site listings into your own tools: your SIEM, ticketing, vendor-risk system or dashboards.
A paid option on a license key. Every response is JSON, listings can be pulled incrementally with a cursor, and each call tells you how much of today's quota is left. The data is the same as on this site: listings are claims made by criminal groups, not confirmed breaches.
Free API and customer API
Public API (/api/v1) | Customer API (/api/v2) | |
|---|---|---|
| Access | No key; limited per address | License key with the API option |
| Leak-site addresses and claim text | Removed | Included |
| Pull only what is new | Page through everything | Cursor: ask for listings after the last one you saw |
| Limits | Shared, can change | Per key, by plan, shown in every response |
| Response shape | Internal fields, can change | Documented and versioned; changes are additions only |
| Vendor lists, exposure check, statistics | Exposure check only | All three |
Start in a minute
Send your key in X-Api-Key, or as Authorization: Bearer. Keep it on your server: it is shown to you once and cannot be recovered.
curl -H "X-Api-Key: ti_your_key" \ "https://tracker.exposuredrift.com/api/v2/listings?limit=2"
{
"data": [{
"id": "k3m9qxa",
"name": "Example Clinic",
"domain": "exampleclinic.com",
"group": {"name": "akira", "slug": "akira"},
"country": {"code": "US", "name": "United States"},
"sector": "Healthcare",
"first_seen": "2026-11-10T08:14:00Z",
"claimed_data_size": "120 GB",
"claim_tags": ["medical"],
"url": "https://tracker.exposuredrift.com/victims/k3m9qxa"
}],
"meta": {"count": 1, "limit": 2, "has_more": true, "next_cursor": "k3m9qxa",
"notice": "Listings are claims published by criminal groups..."}
}
Keep a system up to date
Ask oldest first and keep the last next_cursor. Next time, send it back and you receive only what was stored since.
import requests
KEY = "ti_your_key"
cursor = load_cursor() # empty the first time
while True:
r = requests.get("https://tracker.exposuredrift.com/api/v2/listings",
headers={"X-Api-Key": KEY},
params={"order": "asc", "limit": 200, "cursor": cursor, "country": "US"})
r.raise_for_status()
body = r.json()
for item in body["data"]:
handle(item)
if not body["meta"]["has_more"]:
break
cursor = body["meta"]["next_cursor"]
save_cursor(cursor)
Endpoints
| Request | What it returns |
|---|---|
GET /api/v2/me | Your plan, limits and today's usage. |
GET /api/v2/listings | Listings with filters (since, until, group, sector, country, q, tag) and a sync cursor. |
GET /api/v2/listings/{id} | One listing, with the claim text, the group's own post address and the capture when one exists. |
GET /api/v2/groups | Groups by listing count; search and active filter. |
GET /api/v2/groups/{slug} | A group's counts, sectors, countries, leak sites with addresses, and cited public reporting. |
GET /api/v2/check | Has a domain or company been named? Exact matches counted, possible matches listed apart. |
POST /api/v2/vendors/check | Check a list of vendors in one call; the size depends on the plan. |
GET /api/v2/stats/monthly | Totals, change, top groups, sectors and countries for a month. |
GET /api/v2/stats/sectors/{slug} | Twelve-month view of one sector. |
GET /api/v2/usage | Your calls per day for 30 days. |
Saved suppliers and webhooks
Keep a list of the suppliers you depend on. When a new listing names one, we email the addresses you confirmed and send a signed POST to your webhook. A supplier already named when you add it is shown as named but does not alert: only new listings do. Manage the list on the Your suppliers page or through the API:
| Request | What it does |
|---|---|
GET /api/v2/portfolio/vendors | Your suppliers with where each stands. POST adds up to 1,000 per call ({"vendors":[{"name","domain","note"}]}); DELETE /portfolio/vendors/{id} removes one. |
GET /api/v2/portfolio/alerts | The alerts so far, with a sync cursor like /listings. |
PUT /api/v2/portfolio/webhook | Set {"url": "https://..."} and switch it on. The signing secret is returned once. Also GET, DELETE, POST /webhook/test and POST /webhook/rotate-secret. |
What we send
POST https://hooks.yourcompany.com/threatinsights
Content-Type: application/json
X-ThreatInsights-Event: listing.matched
X-ThreatInsights-Delivery: 1042
X-ThreatInsights-Signature: t=1794300000,v1=5c1f...e9
{
"id": "evt_318", "type": "listing.matched", "created_at": "2026-11-13T09:41:02Z",
"vendor": {"id": 77, "name": "Acme Logistics", "domain": "acme-logistics.com", "note": null},
"match": {"kind": "domain"},
"listing": { ...the same shape as /api/v2/listings/{id}, with claim_text and claim_url... },
"notice": "Listings are claims published by criminal groups..."
}
Check the signature before you trust a delivery
The signature is an HMAC-SHA256 of timestamp + "." + raw body with your signing secret. Compare in constant time, and refuse a timestamp older than five minutes.
import hmac, hashlib, time
def verify(secret: str, raw_body: bytes, header: str) -> bool:
parts = dict(p.split("=", 1) for p in header.split(","))
ts, sig = parts["t"], parts["v1"]
if abs(time.time() - int(ts)) > 300:
return False
expected = hmac.new(secret.encode(), f"{ts}.".encode() + raw_body, hashlib.sha256).hexdigest()
return hmac.compare_digest(expected, sig)
const crypto = require("crypto");
function verify(secret, rawBody, header) {
const p = Object.fromEntries(header.split(",").map(x => x.split("=")));
if (Math.abs(Date.now() / 1000 - Number(p.t)) > 300) return false;
const expected = crypto.createHmac("sha256", secret).update(p.t + "." + rawBody).digest("hex");
return crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(p.v1));
}
Delivery rules
- Answer with any
2xxwithin 10 seconds. Anything else, or no answer, is retried after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours, then given up. A4xxother than 408 and 429 is not retried. - Deliveries can arrive more than once and out of order. Use
idto ignore a repeat. - After 5 deliveries in a row give up, the webhook is switched off and your confirmed addresses are told. Email alerts continue.
- The address must be
https, on a public host name, port 443 or 8443. We do not follow redirects, and we refuse addresses that point at private or internal networks. - Delivery logs are kept for 30 days and shown on the Your suppliers page.
Limits by plan
Counted per key. Each response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset (seconds until 00:00 UTC). When a daily quota is used up the API answers 429 with Retry-After.
| Plan | Calls per day | Calls per minute (heavy endpoints) | Page size up to | Vendors per check |
|---|---|---|---|---|
| Pro | 1,000 | 60 | 100 | 100 |
| Team | 10,000 | 120 | 200 | 250 |
| Enterprise | 100,000 | 300 | 500 | 500 |
Errors
Errors are JSON: {"error": {"code": "...", "message": "..."}}.
| Status | Code | Meaning |
|---|---|---|
| 401 | missing_key, invalid_key | No key sent, or the key is wrong or revoked. |
| 403 | api_not_enabled | The key is valid but does not include the API option. |
| 400 | bad_request, bad_cursor, too_many_vendors | A parameter is missing or not valid; the message says which. |
| 404 | not_found | No such listing, group, sector or path. |
| 429 | quota_exceeded, rate_limited | Daily quota used up, or too many calls in a minute. Wait for Retry-After. |
What to know about the data
- A listing is a claim the group published. Treat it as a lead to check, not a confirmed breach. Every response says so in
meta.notice. first_seenis when we first stored the listing, which can be days or weeks after the attack.heuristic_scoreis a rule-based number from sector, group tier and the data claimed. It is not evidence of harm.- Matching in
/checkand/vendors/checkis exact on domain or full name. Not found is not assurance: many incidents are never listed. - Leak-site addresses and claim text can point at criminal infrastructure. Open them only from an isolated environment.
- Version 2 changes by addition only: new fields and endpoints may appear, existing ones keep their meaning. Anything breaking would be a new version with notice.
How to get access
There is no checkout and no published price: you request access, we reply with a price and a PayPal payment link, and when you have paid we add the API to your license key. Tell us what you want to connect and roughly how many calls a day you expect.