Developer Docs

Developer docs for connected data intelligence.

Start with entity search, enrichment, matching, relationship queries, monitoring, and webhooks — then move into sandbox or production access with Hunter.

Request API access →Explore Search API →

Quickstart

Start with four API surfaces.

  • 01
    Entity Search

    Search across all source types

    Query entities by name, identifier, or attribute across Nominodata, public records, partner feeds, and Hunter-owned data. Returns ranked results with match scores and source lineage.

    POST /api/searchLearn more →
  • 02
    Enrichment

    Expand a record with additional attributes

    Pass an entity identifier and receive all available attributes from every source type — sanctions status, adverse media, PEP classification, known associates, and more.

    POST /api/enrichLearn more →
  • 03
    Matching Engine

    Fuzzy match across name variants

    Submit a name or identifier and receive scored match candidates with NamesPlus expansion, transliteration handling, and confidence-weighted evidence objects.

    POST /api/matchLearn more →
  • 04
    Relationship Engine

    Traverse entity connections

    Query the relationship graph for a given entity. Returns connected entities, relationship types, confidence scores, and the source data that established each connection.

    GET /api/relationships/:entity_idLearn more →
  • 05
    Monitoring & Webhooks

    Watch entities for changes

    Register watch conditions on entities or datasets. Receive webhook events when records change, new relationships are discovered, or watchlist status updates.

    POST /api/monitorsLearn more →

Example

A search request and its response.

Illustrative only. Field names, structure, and response shape reflect the Hunter API design — not live credentials or production data.

Request — POST /api/search
POST /api/search HTTP/1.1
Host: api.hunterdata.ai
Authorization: Bearer <your_token>
Content-Type: application/json

{
  "query": "Meridian Capital Holdings",
  "types": ["entity", "organization"],
  "sources": ["nominodata", "public_records", "partner_feeds"],
  "limit": 5
}
Response — 200 OK
HTTP/1.1 200 OK
Content-Type: application/json

{
  "results": [
    {
      "entity_id": "ent_7f3a9c2d",
      "name": "Meridian Capital Holdings Ltd.",
      "match_score": 0.97,
      "source_lineage": ["nominodata", "public_records"],
      "relationship_count": 14,
      "attributes": {
        "jurisdiction": "Cayman Islands",
        "status": "active",
        "sanctions_hit": false,
        "pep_associated": true
      }
    },
    {
      "entity_id": "ent_2b8e1f44",
      "name": "Meridian Capital Holdings Inc.",
      "match_score": 0.81,
      "source_lineage": ["partner_feeds"],
      "relationship_count": 3,
      "attributes": {
        "jurisdiction": "Delaware, US",
        "status": "dissolved",
        "sanctions_hit": false,
        "pep_associated": false
      }
    }
  ],
  "total": 2,
  "query_id": "qry_a1b2c3d4",
  "latency_ms": 48
}

Response fields

  • entity_id

    Stable identifier for the matched entity across all source types.

  • name

    Canonical name as resolved from the highest-confidence source.

  • match_score

    Confidence score from 0 to 1. Scores above 0.85 indicate high-confidence matches.

  • source_lineage

    Array of source types that contributed data for this result.

  • relationship_count

    Number of known entity connections in the Relationship Engine graph.

  • attributes

    Structured attributes including jurisdiction, status, sanctions, and PEP flags.

Authentication

Access is provisioned, not self-serve.

API access is provisioned after a brief request review. This keeps the data layer clean and ensures each integration is scoped correctly from the start.

Sandbox access is available for qualified evaluations — you get a full-featured token scoped to test data so you can validate your integration before going live.

Request access →
  • Token formatBearer token in the Authorization headerAuthorization: Bearer <your_token>
  • Token scopeScoped to an integration

    A single account can hold multiple tokens with different permission sets. Tokens do not expire but can be rotated at any time.

  • Sandbox accessAvailable for qualified evaluations

    Sandbox tokens are provisioned with test data. They do not count against production rate limits.

  • Rate limitsDefined per integration tier

    Limits are set at provisioning time based on your evaluation or production agreement.

  • ProvisioningReviewed and issued within one business day

    Submit a request via the contact form. Include your use case and expected query volume.

Evaluate

Ready to evaluate Hunter with your records?

Request sandbox access and we’ll provision your credentials within one business day. No commitment required for evaluation.

Request access →