Enterprise APIs expose account-scoped attack-surface and monitoring data. Every route requires an API key associated with an Enterprise account.

​
Endpoint map

Limits are route-specific. They are not uniformly 60 requests per minute.

​
Choose a workflow

  • Use Organizations Management to establish account scope and add owned domains or public IP ranges.
  • Use Alerts for recorded asset and exposure changes.
  • Use Vulnerabilities for findings observed on account assets.
  • Use Entities to group and retrieve related assets.
  • Use Dark Web APIs for compromised credentials, discovered emails, potential phishing, and typosquatting records.
  • Use Certificates for certificate observations and expiry workflows.
  • Use Suggested Domains as a review queue, not automatic proof of ownership.

​
Authentication

The dedicated Enterprise host is https://enterprise-api.fullhunt.io/api/v1/. Using that host does not replace account authorization.

​
Data boundaries

  • Enterprise results are scoped to organizations associated with the authenticated account.
  • Date filters on alerts, certificates, suggested domains, phishing, and typosquatting use DD/MM/YYYY.
  • Potential phishing and typosquatting filters use q; compromised credentials use query.
  • Suggested domains are candidates that require ownership review.
  • Scan requests are asynchronous. The OEM API has a scan-status route; the Enterprise trigger does not.
  1. List organizations and retain their IDs.
  2. Add only assets you own or are authorized to monitor.
  3. Establish a baseline from entities, assets, alerts, and vulnerabilities.
  4. Persist response timestamps and result identifiers outside FullHunt.
  5. Run incremental collection with bounded pagination and retry behavior.