OEM Dark Web Search - FullHunt API Documentation

Request

POST /api/v1/oem/darkweb/search

Field	Required	Description
`type`	Yes	Supported field type
`query`	Yes	Value to search
`no_cache`	No	Set true to bypass the normal 24-hour OEM cache
`query_tags`	No	Tenant and request attribution object

Supported types are username, name, email, hostname, mac_address, ip_address, org_alias, bin, cve, domain, password, hashed_password, vin, address, and phone.

curl "https://fullhunt.io/api/v1/oem/darkweb/search" \
  -H "X-API-KEY: $FULLHUNT_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{
    "type": "domain",
    "query": "customer-domain.example",
    "query_tags": {"tenant_id": "tenant-123"}
  }'

The route is OEM-credited. A cve query can return vulnerability intelligence rather than credential records.

Data controls

Do not display or log raw passwords.
Hashes can still be sensitive and should be access-controlled.
Do not use returned credentials to access another service.
Store source, breach date, ingestion date, tenant, and incident disposition.
Apply retention and deletion requirements before enabling collection.
Restrict free-form searches that could retrieve unrelated personal data.

An empty or 404 response means no result was returned for the query; it does not prove that no exposure exists.