Query file hashes, IP addresses, domains, URLs, CVEs, emails and phone numbers over a token-authenticated REST API. Everything is a GET request, everything returns JSON, and indicators we have not seen yet are fetched live on request.
Create an account to generate a key. Treat it like a password — it carries your plan's quota and it is the only credential the API needs.
Sign in to get a keySend the key in the Authorization header on every request.
Authorization: Token <your-api-key>
Every lookup takes a query parameter. This one asks what we know about a domain.
curl -H "Authorization: Token $TFA_TOKEN" \
"https://api.threatfusionai.com/domain-lookup/?query=google.com"{
"value": "google.com",
"indicator_type": "domain",
"score": { "value": 5 },
"detections": {
"flagged": 1,
"total_engines": 91,
"risk": "Low"
},
"categories": [ "Information Technology", "AI/ML Applications" ],
"corr": { "ips": [ "74.125.69.102", "…" ] }
}Seven indicator types, one consistent response shape.
| Indicator | Endpoint | |
|---|---|---|
| File hash | /hash-lookup/ | |
| IP address | /ip/ · /ip-lookup/ · /ip-geo/ | |
| Domain | /domain-lookup/ · /domain/ | |
| URL | /url-lookup/ · /url/ | |
| CVE | /cve/ · /cves-data/ | |
/email-lookup/ | ||
| Phone | /phone-lookup/ | |
| Any indicator | /ioc-crossref/ · /mitre-attribution/ |
?wait=N to blockEvery endpoint, every parameter, and a real captured response for each one.
Open the API referenceAI assistant — can make mistakes. Verify important results.