FullContact Enrich API

Name: FullContact Enrich API API
Brand: FullContact Enrich API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentContact Enrichmentbearer9 EndpointsREST

For Agents

Enrich person records from email, phone, or social identifiers and resolve fragmented customer identities into unified profiles with demographics, employment, and social data.

Connect the FullContact Enrich API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FullContact Enrich API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with FullContact Enrich API API.

Enrich person profiles from email, phone, name, social handle, or mobile ad ID inputs

Look up company firmographics including employee count, industry, and founding year from a domain

Resolve fragmented customer identifiers into a unified PersonID across the Identity Graph

Map and merge customer records from multiple touchpoints into a single identity

GET STARTED

Start building with FullContact Enrich API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for FullContact Enrich API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for FullContact Enrich API, keeping it validated and agent-ready. Resolve fragmented person and company identifiers — emails, phones, names, addresses, social profiles, or MAIDs — into unified contact records with demographics, employment history, and social data. The Identity Graph maps and resolves disparate customer touchpoints to a single PersonID, enabling cross-channel identity resolution across 9 endpoints.

Use Cases

Patterns agents use FullContact Enrich API API for, with concrete tasks.

★ AI Agent Contact Enrichment via Jentic

AI agents processing inbound leads can enrich sparse contact data by querying FullContact through Jentic. The agent passes an email address and receives a full profile including name, job title, company, social links, and demographics — enabling instant lead scoring and routing without manual research.

Search Jentic for 'enrich person by email', load the FullContact person.enrich schema, and submit a POST with email 'jane@example.com' to retrieve her full profile

Cross-Channel Identity Resolution

Marketing platforms receiving customer interactions across email, phone, web, and mobile need to unify those touchpoints into a single customer view. FullContact's identity.mapResolve endpoint combines mapping and resolution in one call, returning a stable PersonID with all associated identifiers so teams can deduplicate records and personalise outreach.

POST to /identity.mapResolve with recordId 'crm-12345', email 'jane@example.com', and phone '+14155551234' to get the unified PersonID and all linked identifiers

Company Enrichment for Account-Based Marketing

Sales teams targeting specific accounts enrich company records by domain to get firmographic data including industry, employee count, founding year, location, and social profiles. This powers account scoring and helps reps tailor outreach to the prospect's company context.

POST to /company.enrich with domain 'hubspot.com' and retrieve the company name, employee count, industry, and LinkedIn profile

Customer Record Tagging for Segmentation

CRM and CDP platforms tag resolved customer records with custom labels for audience segmentation. FullContact's tags endpoints let you attach, retrieve, and remove key-value tags on any customer recordId, enabling dynamic segment membership without modifying the core identity data.

POST to /tags.create with recordId 'crm-12345' and tags [{"key": "segment", "value": "enterprise"}, {"key": "lifecycle", "value": "qualified"}]

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for fullcontact enrich api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/person.enrich

Enrich person data from multi-field identifiers

POST

/company.enrich

Enrich company data by domain

POST

/identity.map

Map customer identifiers to the Identity Graph

POST

/identity.resolve

Resolve identifiers to a PersonID with all linked data

POST

/identity.mapResolve

Map and resolve in a single call

POST

/identity.delete

Delete a mapped customer record from the graph

POST

/tags.create

Create key-value tags on a customer record

POST

/person.enrich

Enrich person data from multi-field identifiers

POST

/company.enrich

Enrich company data by domain

POST

/identity.map

Map customer identifiers to the Identity Graph

POST

/identity.resolve

Resolve identifiers to a PersonID with all linked data

POST

/identity.mapResolve

Map and resolve in a single call

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

FullContact Bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access — raw API keys never enter the agent's context window.

Intent-based discovery

Agents search by intent (e.g., 'enrich a person from their email') and Jentic returns matching FullContact operations with their input schemas, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct FullContact integration: 2-4 days for auth, identity graph setup, and error handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Clearbit Logo API

Retrieves company logos by domain to visually enrich contact cards alongside FullContact profile data

Use Clearbit Logo when you need visual brand assets (logos) to accompany the textual contact data from FullContact.

Alternative

People Data Labs API

Large-scale person and company enrichment with SQL-like search queries across a 3+ billion record dataset

Use People Data Labs when you need bulk search with SQL-like queries, broader dataset coverage, or enrichment by job title and skills — FullContact excels at multi-identifier resolution and identity graphing.

Complementary

Hunter API

Finds and verifies professional email addresses for a domain, which can feed into FullContact enrichment

Use Hunter when you need to discover email addresses first, then pass them to FullContact for full profile enrichment.

FAQs

Specific to using FullContact Enrich API API through Jentic.

Why is there no official OpenAPI spec for FullContact Enrich API?

FullContact does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call FullContact Enrich API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the FullContact Enrich API use?

The API uses a Bearer token in the Authorization header. Your FullContact API key is passed as 'Bearer {api_key}' on every request. Through Jentic, this token is stored encrypted in the credential vault and injected automatically — agents never see the raw key.

Can I enrich a person from just a phone number with the FullContact API?

Yes. The /person.enrich endpoint accepts a phone or phones field as an identifier. International numbers require country codes. You can combine phone with other identifiers (email, name, social profiles) for higher match rates — up to 25 emails and 25 phones per request.

What is the difference between identity.map and identity.resolve?

The /identity.map endpoint adds identifiers to the Identity Graph under a client-provided recordId. The /identity.resolve endpoint looks up a record and returns all associated identifiers and PersonIDs. Use /identity.mapResolve to do both in a single call.

How do I enrich a contact through Jentic?

Install the SDK with pip install jentic, then search for 'enrich person by email'. Jentic returns the FullContact /person.enrich operation schema. POST with your identifier (email, phone, or social profile) and Jentic handles auth and returns the enriched profile.

What data does the person enrichment response include?

The response returns fullName, ageRange, gender, location, job title, organization, Twitter handle, LinkedIn URL, bio, and avatar. With Insights Bundles enabled, you also get detailed demographics, full employment history, education, interests, and associated URLs.