Skip to main content

Return to Documentation Overview

Overview

The Huckle Insights API gives you programmatic access to the same audience intelligence that powers the platform. Use it to match and enrich your first-party contact lists, estimate audience sizes, preview results before a full query, and monitor your usage — all from within your own applications and workflows.

Audience Search

Submit contact records and receive enriched profiles in return

Audience Preview

Preview a sample of matched results before running a full search

Audience Estimate

Estimate how many records match a given set of criteria

Audience Search Usage

Monitor record consumption against your plan limits

Authentication

All API requests are authenticated using an API key passed as a request header.
Authorization: Bearer YOUR_API_KEY
API keys are generated once and hashed before storage. The plaintext key is only shown at creation — store it securely. Keys can be revoked at any time from Settings > Developer.

Who Can Generate API Keys

API key access is limited to Owners and Admins. Members and Viewers cannot access developer settings. See Roles & Permissions for a full breakdown.

Generating a Key

  1. Navigate to Account Settings > Developer settings in the Huckle Insights platform.
  2. Click Generate API Key.
  3. Copy and store the key immediately — it will not be shown again.
API key generation is only available if your organization is enabled for API usage. Please reach out to support@huckleinsights.com to enable the API.

Base URL

All API endpoints are relative to the following base URL:
https://api.huckleinsights.com/v1

Request Format

All requests use JSON. Set the Content-Type header accordingly:
Content-Type: application/json

Input Requirements

The API matches records against a database of 260 million U.S. adult profiles. For a record to be eligible for matching, it must include at minimum one of the following field combinations:
OptionRequired Fields
AFirst Name + Last Name + Email Address
BFirst Name + Last Name + Full Address + ZIP Code
Records that do not meet the minimum requirements will return a Level 5 (No Match) result. See Huckle Match for a full explanation of match levels.

Match Levels

Every record returned by the API includes a match level indicating the quality of the match found. See Match Levels in the Huckle Match guide for the full breakdown.

Response Fields

Matched records are enriched with 350+ data attributes spanning ten categories. The fields returned depend on your plan and the fields requested in the API call.

Individual / Address

26 Fields — Names, address components, age, gender

Geographic

10 Fields — Region, CBSA, county, urbanicity

Household Demographics

26 Fields — Income, education, household composition

Telephone

6 Fields — Up to 3 phone numbers with DNC flags

Real Estate

4 Fields — Ownership status, home value

MarketShare Demographics

72 Fields — Purchase behavior and transaction data

Consumer Passions Index

107 Fields — Interest and affinity indices (0–9 scale)

Connex Clusters

9 Fields — Lifestyle and media consumption segments

Connex Targets

51 Fields — Household-level consumer propensity scores

Census Demographics

27 Fields — Interpolated Census data by ZIP code
See the Data Dictionary for the full list of available fields, formats, and value descriptions.
For most integrations, this is the typical call sequence:
1

Estimate your audience

Call Audience Estimate with your target criteria to understand how many records are available before committing any of your plan’s match record quota.
2

Preview a sample

Call Audience Preview to inspect a representative sample of matched records and verify that the fields and match quality meet your needs.
3

Run a full search

Call Audience Search to retrieve the full enriched result set. This is the call that consumes records from your monthly quota.
4

Monitor usage

Call Audience Search Usage to track how many records have been consumed against your plan limit for the current billing period.

Security

All API traffic is encrypted in transit using TLS 1.2 or higher. API keys are generated using cryptographically secure methods and are never stored in plaintext. See Security & Cryptography for full details.

Data Privacy

Your submitted contact data is never used to train models or update the Huckle database. All data is processed in a secure, isolated environment. Huckle is compliant with all applicable state and federal data privacy standards.

What’s Next?

Data Dictionary

Explore the full set of fields available in API responses

Huckle Match — User Guide

Understand how the matching algorithm works

Roles & Permissions

Understand who can generate and manage API keys

Security Practices

How Huckle protects your data in transit and at rest