Introduction

Send us a domain. We send back the company: name, headcount, industry, headquarters, LinkedIn page. Send us a LinkedIn profile URL or a work email. We send back the person and their employment history. Built for pipelines. Signups, CRM records, lead lists, anything that needs firmographic or people data attached to it.

What you can enrich

Companies

Domain or LinkedIn company URL in. Firmographics out.

People

LinkedIn profile URL in. Profile and employment history out.

Reverse email lookup

Work email in. The confirmed LinkedIn profile behind it out.

How a request flows

Every enrichment is a task. You create one, we work it, you collect the result.

You send an input

A domain, a LinkedIn URL, or a work email address.

We check what we already hold

If we have a fresh record, the task settles inside the same request. You get 200.

Otherwise we go and get it

We resolve the input, pull the source, and store the result. You get 202 and a task id.

You collect the result

Poll the task, or have it pushed to your webhook through a Loop.

Companies we already hold come back in the same request. New companies take seconds to low tens of seconds. Reverse email lookups take longer, because we resolve them live.

Two ways to get results

You can call an enrichment endpoint directly, or send the same input through a Loop. A Loop is a webhook destination you create once in the dashboard.

	Direct request	Loop
Endpoint	`POST /v1/companies/enrich` or `POST /v1/people/enrich`	`POST /v1/loops/{id}/run`
What gets enriched	Decided by the endpoint you call	Decided by the Loop’s configuration (company or person)
How you get the result	Poll `GET /v1/tasks/{id}`	We `POST` it to your webhook. You can still poll.
Setup	An API key	An API key and a Loop
Good for	Scripts, one-off lookups, low volume	Pipelines, CRM sync, anything that should not sit and wait

Both return the same task object and cost the same credits. Pick a Loop when you don’t want to hold a connection open while we work. See Loops and webhooks.

Quick start

Enrich a company by domain:

curl -X POST "https://api.enrichloops.com/v1/companies/enrich" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"stripe.com"}'

You get a task back. Never the company data inline, even when we already hold the company:

{
  "task": {
    "id": "8bf3d449-e013-4faa-8994-a6d25031e001",
    "object_type": "company",
    "operation": "enrich",
    "status": "succeeded",
    "target": "stripe.com",
    "credits_charged": 1,
    "created_at": "2026-08-07T23:21:32.481Z"
  }
}

200 means the task already settled. 202 means it is queued. Either way, fetch the result from the task:

curl "https://api.enrichloops.com/v1/tasks/8bf3d449-e013-4faa-8994-a6d25031e001" \
  -H "Authorization: Bearer YOUR_API_KEY"

{
  "task": { "...": "...", "status": "succeeded" },
  "data": {
    "name": "Stripe",
    "domain": "stripe.com",
    "linkedin_url": "https://www.linkedin.com/company/stripe",
    "employee_count": 8000,
    "employee_range": "5001-10000",
    "primary_industry": "Financial Services",
    "headquarters": { "city": "San Francisco", "country": "United States" }
  }
}

data appears once task.status is succeeded. error appears once it is failed. Poll every 2 seconds until the status is one of those two.

Next steps

Authentication

Get an API key and send your first request.

Tasks, polling and errors

The task object, status codes, error codes, credits and rate limits.

Loops and webhooks

Stop polling. Get results pushed to you.

API reference

Full request and response schemas for every endpoint.

Get started

Enrichment

Webhook delivery

What you can enrich

Companies

People

Reverse email lookup

How a request flows

Two ways to get results

Quick start

Next steps

Authentication

Tasks, polling and errors

Loops and webhooks

API reference

​What you can enrich

Companies

People

Reverse email lookup

​How a request flows

​Two ways to get results

​Quick start

​Next steps

Authentication

Tasks, polling and errors

Loops and webhooks

API reference

What you can enrich

How a request flows

Two ways to get results

Quick start

Next steps