FullEnrich API

Name: FullEnrich API
Brand: FullEnrich API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentContact Enrichmentbearer8 EndpointsREST

For Agents

Enrich B2B contacts with email and phone, reverse-lookup an email to a person, and search people or companies across 20+ providers.

Install Jentic One Beta

Connect the FullEnrich API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FullEnrich 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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 FullEnrich API.

Submit bulk contact enrichment jobs spanning 20+ underlying providers

Poll a bulk enrichment job by ID until results are ready

Reverse-lookup an email to identify the person behind it

Search for people matching name, role, or company filters

GET STARTED

Start building with FullEnrich API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use FullEnrich API for, with concrete tasks.

★ Bulk Lead Enrichment

Sales operations teams upload a list of LinkedIn URLs or names plus companies and need verified work emails for outbound. POST /contact/enrich/bulk submits the batch and returns an enrichment_id; GET /contact/enrich/bulk/{enrichment_id} returns the matched records once the underlying providers have responded. FullEnrich's waterfall typically lifts match rates over single-provider tools.

Submit a bulk enrichment job with 100 LinkedIn URLs and poll the enrichment_id every 30 seconds until complete

Reverse Email Lookup

Given only an email captured in a webform or a calendar invite, POST /contact/reverse/email/bulk identifies the person, their employer, and verified contact channels. GET /contact/reverse/email/bulk/{enrichment_id} returns the resolved profile. Useful for lead routing inside a CRM when only the email is known.

Submit a reverse-email job for sales@example.com and retrieve the resolved name, role, and company

Targeted People Search

Marketing and sales teams build target lists by attributes rather than starting from a known contact. POST /people/search returns matching profiles for queries such as job title, seniority, and company size. The results can be fed back into bulk enrichment to verify the email and phone before outreach.

Search FullEnrich for VPs of Engineering at SaaS companies with 100-500 employees in the United States

Account Credit and Key Health

Before launching a large enrichment job, an operations script calls GET /account/credits to confirm sufficient credits and GET /account/keys/verify to confirm the API key is active. This avoids partial-batch failures and surfaces low-credit conditions to the team in advance.

Call GET /account/credits and alert if credits remaining is below 1000

Agent-Driven Lead Workflow

An AI agent inside a sales workflow takes a list of LinkedIn URLs from a chat prompt, kicks off a bulk enrichment, polls for results, and writes the verified emails into a downstream CRM. Through Jentic the bearer token is vaulted and the agent only sees scoped enrichment results.

Search Jentic for 'enrich a list of contacts', load POST /contact/enrich/bulk, execute with 50 rows, and poll GET /contact/enrich/bulk/{enrichment_id}

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/contact/enrich/bulk

Submit a bulk contact enrichment job

GET

/contact/enrich/bulk/{enrichment_id}

Retrieve results for a bulk enrichment job

POST

/contact/reverse/email/bulk

Submit a reverse email lookup job

GET

/contact/reverse/email/bulk/{enrichment_id}

Retrieve reverse-email results

POST

/people/search

Search for people by filters

POST

/company/search

Search for companies by firmographics

GET

/account/credits

Check remaining account credits

POST

/contact/enrich/bulk

Submit a bulk contact enrichment job

GET

/contact/enrich/bulk/{enrichment_id}

Retrieve results for a bulk enrichment job

POST

/contact/reverse/email/bulk

Submit a reverse email lookup job

GET

/contact/reverse/email/bulk/{enrichment_id}

Retrieve reverse-email results

POST

/people/search

Search for people by filters

Why Jentic?

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

Credential isolation

FullEnrich bearer tokens are stored encrypted in the Jentic MAXsystem vault. Agents call enrichment operations via scoped execution tokens, and the bearer token is injected into the Authorization header only at execution time.

Intent-based discovery

Agents search Jentic for intents like 'enrich a list of contacts' or 'find the person behind an email' and Jentic returns the matching POST /contact/enrich/bulk or POST /contact/reverse/email/bulk operation with its input schema, so the agent submits the right batch shape on the first try.

Time to first call

Direct FullEnrich integration: 1-2 days for bearer auth, batch submission, polling, and credit-aware retry logic. Through Jentic: under an hour — search, load, execute.

FAQs

Specific to using FullEnrich API through Jentic.

Why is there no official OpenAPI spec for FullEnrich API?

FullEnrich does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call FullEnrich 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 FullEnrich API use?

FullEnrich uses bearer-token authentication. The token is generated in the FullEnrich dashboard and presented as Authorization: Bearer <token>. Jentic stores the bearer token encrypted in the MAXsystem vault and injects it at execution time.

Can I run reverse email lookups in bulk through FullEnrich?

Yes. POST /contact/reverse/email/bulk submits a batch of emails for resolution and returns an enrichment_id. Poll GET /contact/reverse/email/bulk/{enrichment_id} to retrieve the resolved person, role, and company.

What are the rate limits for the FullEnrich API?

FullEnrich rate-limits per account, with bulk operations consuming credits rather than synchronous request quota. Keep concurrent jobs low and rely on the asynchronous bulk pattern for large lists; do not poll a single enrichment_id more often than every 15-30 seconds.

How do I check my account credits through Jentic?

Search Jentic for 'check fullenrich credits', load the GET /account/credits schema, and execute. The response returns the credit balance so an operations agent can alert before a large bulk job begins.

Is the FullEnrich API free?

FullEnrich operates on a paid credit model. Each enriched record consumes credits regardless of which underlying provider supplied the match. There is typically a free trial credit allotment for new accounts.

FullEnrich API

Connect the FullEnrich API to your agent

Capabilities

Start building with FullEnrich API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs