Global Search

​

Access and credits

• Community keys need available credits. Each successful request deducts one credit.
• Enterprise accounts use the Global Search module:
  • The module must be enabled for the account; otherwise the route returns 403 “Global Search module is not enabled”.
  • If the account has a filter allow-list, every filter in the request must be on it (aliases such as tags are checked by their canonical name, tag). A filter outside the list returns 403 “Filter not enabled for your account: …”. An account without an allow-list may use every filter.
  • Each successful request deducts one credit from the account’s Global Search credit pool, not from its regular credits. An empty pool returns 403 “You have no remaining Global Search credits”.
  • Accounts with Global Search vulnerability access also receive each host’s vulnerabilities field; other callers do not.

​

Request

POST /api/v1/global/search

curl "https://fullhunt.io/api/v1/global/search" \
  -H "X-API-KEY: $FULLHUNT_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{
    "country": "CA",
    "product": "Apache",
    "port": 443,
    "page": 1
  }'

​

Filters

​

Response behavior

• Page size is limit (default 50, maximum 200); the response’s page_size reports it.
• total_query_results is capped for display.
• total_pages is derived from the displayed count.
• A successful authenticated request consumes one credit (Enterprise: from the Global Search pool). The response’s credits field is the remaining balance.
• Results omit selected heavy internal fields.