Get API key

Data enrichment API

Data enrichment API for public professional & company data

Enrich people, company, and CRM records with structured public professional data through clean JSON responses built for B2B workflows.

Get API keyView docs

100 free credits · No credit card required

What you get

  • Public professional data
  • People and company records
  • Clean JSON
  • Developer docs
  • API-ready workflows

Coverage

What EnvoAPI enriches

Add professional and company context to incomplete records, reducing manual research and improving data workflows. EnvoAPI helps teams enrich people, company, CRM, and business records with structured public professional data through API access.

  • People records

    Resolve public profile records and enrich professional context such as names, headlines, locations, positions, education, skills, counts, and section availability when returned.

    • CRM contacts
    • Lead records
    • Recruiting databases
    • Sales intelligence lists

  • Company records

    Resolve companies by documented identifiers, then add account-level context such as company name, domain-related matches, industry, website, employee range, jobs, posts, products, and insights.

    • Account records
    • Market research datasets
    • B2B SaaS account records
    • Data warehouse records

  • Workflow records

    Map EnvoAPI responses back to your internal IDs, CRM objects, queue jobs, data pipeline rows, or AI workflow inputs without exposing API keys in browser code.

    • Internal business systems
    • Marketing workflows
    • Custom pipelines
    • AI workflow inputs

Inputs

Supported enrichment inputs

Start enrichment with supported identifiers such as profile URLs, company references, CRM records, and endpoint-specific inputs. EnvoAPI supports enrichment workflows based on available identifiers, endpoint type, data coverage, and data availability.

Supported input examples

  • LinkedIn profile URL
  • Public profile identifier
  • Company URL
  • Company domain
  • Company name
  • Company universal name
  • Company page reference
  • Existing CRM contact record
  • Existing company record
  • Job or hiring-related context
  • Public professional data reference
  • Internal record ID

Input support may depend on endpoint type, plan, match rate, and available public data sources. Keep your internal record IDs in your own system and map them back to the response.

Documented entry points

Profile inputs

Use documented profile endpoints when you have a public profile URL, public identifier, or internal profile ID returned by a previous EnvoAPI response.

  • /api/v2/profiles/detail?url=...
  • /api/v2/profiles/{public_identifier}
  • /api/v2/profiles/id/{profile_id}

Company inputs

Use company endpoints when you have a website domain, company URL, universal name, or company ID supported by the current OpenAPI contract.

  • /api/v2/companies/by-domain?domain=...
  • /api/v2/companies/detail?url=...
  • /api/v2/companies/{universal_name}

Search and discovery inputs

Use search endpoints to discover people, companies, posts, filters, typeahead suggestions, and locations before choosing the enrichment endpoint to call next.

  • /api/v2/search/people?keywords=...
  • /api/v2/search/companies?keywords=...
  • /api/v2/search/filters?result_type=...

Job and hiring-context inputs

Use job endpoints and company job endpoints for hiring-signal workflows where listings, job details, and company-level open role context are relevant.

  • /api/v2/jobs/search?keywords=...
  • /api/v2/jobs/detail?url=...
  • /api/v2/companies/{universal_name}/jobs

12 entry points across 4 input families. The full parameter set, response schemas, and error states are in the reference.View API documentation

Schema

Returned data fields

Review the people, company, and job-related fields EnvoAPI may return for mapping, storage, and workflow planning. 34 example fields, grouped by the record they belong to, ready to map into CRMs, recruiting platforms, dashboards, data warehouses, and internal systems.

People data

12 fields
  • Full name
  • Headline
  • Current job title
  • Current company
  • Location
  • Industry
  • Public identifier and profile URL
  • Positions and work experience
  • Education
  • Skills
  • Follower and connection counts
  • Public professional sections when available

Company data

11 fields
  • Company name
  • Universal name and company profile URL
  • Website URL and domain match
  • Company description
  • Industry
  • Employee count and size range
  • Locations
  • Specialities
  • Follower count
  • Jobs, posts, products, and insights when available
  • Firmographic and business details when available

Job and hiring-context data

11 fields
  • Job title
  • Company
  • Location
  • Workplace and employment type
  • Job URL
  • Job description and posted text
  • Job details
  • Company open-job count
  • Search filters
  • Hiring signals when available
  • Role demand and expansion context when available

Available fields may depend on endpoint type, input quality, data depth, data freshness, data availability, source availability, rate limits, and plan.

Compare

Person vs company enrichment

Compare person-level and company-level enrichment to decide what context your B2B workflow needs. Use person enrichment when the workflow needs contact-level professional context; use company enrichment when it needs account-level business context.

Person enrichment

7 workflows

Use person enrichment when the workflow needs contact-level professional context.

  • Lead qualification
  • Talent research
  • Contact segmentation
  • Recruiting workflows
  • Sales intelligence
  • Job title analysis
  • Sales process support

Company enrichment

8 workflows

Use company enrichment when the workflow needs account-level business context.

  • Account enrichment
  • Company research
  • CRM account enrichment
  • Firmographic enrichment
  • Territory planning
  • Market mapping
  • Industry analysis
  • Hiring analysis

Use both together.Many B2B workflows need both person and company data. A CRM may need a contact's role and location, plus company size, industry, domain, website, and business details for account-level scoring — one record, scored at both levels.

The enrichment run

From an identifier to a mapped record

Four steps, one round trip. Each one hands the next a named part of the response, and the last one hands it to you.

  1. 01

    Send an identifier

    A profile URL, public identifier, company domain, universal name, or search keyword — whatever the record you already hold gives you.

    You sendurlpublic_identifierdomainkeywords

  2. 02

    Resolve the record

    EnvoAPI matches the input to a public person or company record and reports what it resolved to.

    Returned inmeta.resolved

  3. 03

    Attach the context

    Structured professional and company fields are added when available — positions, education, skills, firmographics, hiring context.

    Returned indata

  4. 04

    Map it back

    One documented envelope, the same shape on every endpoint, mapped onto your own record IDs in your own system.

    Envelopesuccessdatapaginationmeta

Example call

Example API request and JSON response

Preview how an enrichment request and JSON response look before planning your integration — a synthetic profile record and the documented v2 envelope. Run production calls from a server-side integration layer so API keys stay out of browser code.

Try it in the Playground

The response envelope

  • success
  • data
  • pagination
  • meta

Every endpoint answers with the same top-level keys, so a field mapping built once survives swapping the call. Collection responses also fill pagination.

Request

Profile enrichment request

GET/api/v2/profiles/detailbash
curl -G https://api.envoapi.com/api/v2/profiles/detail \  -H "X-API-Key: $ENVO_API_KEY" \  --data-urlencode "url=https://www.linkedin.com/in/avery-chen-synthetic/"

Response

Synthetic profile response

Response200application/jsonjson
{  "success": true,  "data": {    "profileId": "synthetic-profile-001",    "fullName": "Avery Chen",    "firstName": "Avery",    "lastName": "Chen",    "headline": "Revenue operations leader at Northstar Systems",    "publicIdentifier": "avery-chen-synthetic",    "location": {      "fullLocation": "San Francisco Bay Area",      "country": "United States",      "countryCode": "US"    },    "followerCount": 1840,    "connectionCount": 500,    "industry": {      "name": "Software Development"    },    "skills": [      { "name": "Revenue operations" },      { "name": "Data operations" }    ],    "positions": [      {        "title": "Head of Sales",        "companyName": "Northstar Systems",        "location": "San Francisco, CA",        "startDate": {          "year": 2022,          "month": null,          "day": null        },        "endDate": null      }    ]  },  "pagination": null,  "meta": {    "operation": "full_profile",    "input": {      "url": "https://www.linkedin.com/in/avery-chen-synthetic/"    },    "resolved": {      "publicIdentifier": "avery-chen-synthetic",      "profileId": "synthetic-profile-001"    },    "cache": {      "hit": false    },    "note": "Synthetic example for public documentation."  }}

This response structure helps developers map enriched data into CRMs, recruiting tools, sales intelligence platforms, data warehouses, dashboards, AI agents, and B2B SaaS products.

Workflows

Data enrichment API use cases

See how teams use enriched people and company data across CRM, sales, recruiting, SaaS, and research workflows — built for GTM teams, data teams, and product teams that need structured professional data connected directly to existing systems.

  • CRM enrichment

    Improve incomplete people and company records for segmentation, scoring, routing, research, and sales workflows.

  • Sales intelligence

    Enrich lead and account records with professional and company data for prospect research, account intelligence, lead scoring, and outbound workflows.

  • Recruiting platforms

    Use people, company, and job-related data to support talent research, candidate discovery, job title analysis, and hiring intelligence.

  • B2B SaaS products

    Add professional and company data into SaaS dashboards, account intelligence features, user records, and product workflows.

  • Marketing teams

    Use enriched company and account data to improve segmentation, campaign targeting, market analysis, and GTM planning.

  • Data teams

    Send structured enrichment outputs into data warehouses, custom pipelines, internal databases, and reporting systems.

  • AI workflows

    Use enriched data as structured context for AI agents, research automation, account analysis, and internal decision-support workflows.

7 workflows listed. The list is not the boundary — anything that can send an HTTP request with a custom header can enrich a record, including your own cron job, queue worker, or serverless function.

Alternatives

How EnvoAPI compares to other data enrichment APIs

This comparison is written by the team behind EnvoAPI, which is one of the options below. The assessments are our reading of how each product is positioned rather than a measured benchmark — verify coverage against your own record set before you commit.

Data enrichment providers by shape
ProviderData typesIntegration shapeBest for
EnvoAPIProfiles, companies, jobsUnified REST APIOne API for profile, company, and job enrichment
CoresignalCompanies, jobs; narrower profilesDatasetLarge-scale workforce and job-market analytics
People Data LabsProfiles, companies; no job listingsDataset and APIPerson and company enrichment for CRM and CDP
Bright DataProfiles, companies; limited jobsScraper API and datasetsReal-time scraping and web data infrastructure
LinkdAPIProfiles, companies; limited jobsLinkedIn-focused APIA near drop-in swap for Proxycurl-shaped endpoints
ApifyProfiles, jobs; narrower companiesActors and automationCustom LinkedIn automation and orchestration

6 providers compared. The split that matters most is shape: a unified enrichment API, a bulk dataset, a scraping platform, or a workflow runner.

Read the full provider comparison

Developers

Built for developer workflows

Evaluate EnvoAPI with authentication, JSON responses, examples, documentation, rate limits, and integration guidance — designed for developers who need programmatic access to structured data, predictable responses, and clear integration paths.

Read documentationView API reference

What developers get

  • REST API endpoints
  • API key authentication with X-API-Key
  • Clean JSON responses
  • Request and response examples
  • Error handling guidance
  • Rate limit information
  • Pagination guidance with nextOffset and cursor support
  • Python examples where available
  • SDK examples when available
  • Developer documentation
  • Server-side integration patterns
  • Usage-based scaling
  • CRM integration support
  • Data warehouse and custom pipeline support

Bulk enrichment

EnvoAPI can support enrichment workflows for multiple people, company, or CRM records by calling documented endpoints from a server-side queue or pipeline. Bulk support, request volume, rate limits, match rate, and available fields may depend on endpoint type, usage plan, and data availability.

Compliance

Public data and responsible use

EnvoAPI is a third-party API for public professional and company data workflows. It is not an official LinkedIn product. Review your use case, applicable laws, platform terms, privacy requirements, and internal compliance standards before scaling enrichment workflows.

Important distinction

For OAuth flows, authenticated LinkedIn users, LinkedIn Ads, campaign creation, conversion tracking, Marketing API use cases, or partner-approved features, review official LinkedIn products and partner access requirements.

Data quality note

Data coverage, depth, freshness, and returned fields may vary by input, endpoint, source availability, and plan. Test the workflows that matter to you before scaling production usage.

FAQ

FAQs about the data enrichment API

Quick answers about inputs, returned fields, bulk support, public data handling, documentation, and EnvoAPI's positioning — filed the way the docs are.

What enrichment is

4 questions

What is a data enrichment API?

A data enrichment API helps developers add missing or structured information to existing records such as CRM contacts, company profiles, lead records, recruiting databases, data warehouses, or internal business systems.

Can I enrich both people and company records?

Yes. EnvoAPI supports both person enrichment and company enrichment workflows through separate documented endpoints. Many B2B workflows combine both for contact-level and account-level context.

How does EnvoAPI compare to other data enrichment APIs?

Providers differ most by integration shape. EnvoAPI is a unified REST API for profile, company, and job enrichment; alternatives such as Coresignal and People Data Labs lead with bulk datasets, Bright Data with scraping infrastructure, and Apify with workflow automation. EnvoAPI is one of the options in that comparison, so treat the framing as positioning rather than a benchmark and verify coverage against your own records.

Is EnvoAPI an official LinkedIn API?

No. EnvoAPI is a third-party API and is not an official LinkedIn product. For OAuth, authenticated users, LinkedIn Ads, Marketing API, campaign creation, or partner-approved use cases, teams should review official LinkedIn products and access requirements.

Inputs, fields, and volume

3 questions

What identifiers can I send to EnvoAPI?

Supported identifiers depend on the endpoint. Current examples include profile URLs, public profile identifiers, internal profile IDs returned by EnvoAPI, company URLs, company domains, company universal names, company IDs, search keywords, job URLs, and filter-discovery inputs.

What data fields are returned?

The API can return structured JSON responses with people, company, search, post, and job-related fields when available. Example fields include full name, headline, location, positions, education, skills, company name, website, industry, employee range, job title, and hiring-context fields.

Does EnvoAPI support bulk enrichment?

EnvoAPI can support multi-record enrichment workflows by calling documented endpoints from a server-side queue or pipeline. Request volume, rate limits, match rate, and available fields depend on endpoint type, plan, and data availability.

Where enriched records land

2 questions

Can EnvoAPI support CRM integrations or data warehouse workflows?

Yes. EnvoAPI can support workflows where enriched data is mapped into CRMs, internal databases, dashboards, data warehouses, custom pipelines, and B2B SaaS products.

Can I use EnvoAPI for account enrichment?

Yes. EnvoAPI can support account enrichment by adding company-level context such as company name, website, industry, employee range, locations, jobs, products, posts, and business details when available.

Public data and docs

2 questions

How is public data handled?

EnvoAPI is designed for workflows involving public professional and company data. Teams should review their use case, applicable laws, privacy requirements, platform terms, and internal compliance standards before scaling enrichment workflows.

Do you provide developer documentation?

Yes. The EnvoAPI docs include endpoint details, request examples, response examples, authentication guidance, pagination guidance, rate-limit notes, and error handling guidance for developers.

11 questions filed. Endpoint-level parameters, response schemas, pagination, and error states are already written down.

Review the API reference

Start enriching

Start enriching data with EnvoAPI

Enrich incomplete records with structured public professional data and connect cleaner people, company, job, and account context to your product, CRM, recruiting tool, sales intelligence workflow, data warehouse, or internal system.

Get API keyView docs

100 free credits · No credit card required · 47 API endpoints