Get API key

AboutIndependent LinkedIn data API

About EnvoAPI

EnvoAPI is an API for public professional data. Send a LinkedIn profile URL, a company domain, a job search, or an email address, and get back clean JSON you can store, sync to a CRM, or show in your product. We are an independent company, not affiliated with LinkedIn, and every endpoint is documented in the open.

Get API keyView API documentation

100 free credits · No credit card required · 58 documented endpoints

ONE RESPONSEProfile25 endpointsCompany11 endpointsSearch8 endpointsJobs2 endpointsPosts6 endpointsEmail3 endpointsWebsites3 endpoints

What it does

What EnvoAPI does

EnvoAPI turns public professional data into API responses. You call one of 58 endpoints with an API key. You get back JSON with the same two top-level keys every time: data holds the record, and meta holds the credit cost and the paging.

Seven families cover the data most B2B teams need. Each links to its own page.

  • Profile25 endpoints

    Enrich professional profiles with experience, education, skills, certifications, courses, public contact availability, and activity. Resolve by URL, username, or ID.

  • Company11 endpoints

    Retrieve firmographics, people, products, posts, and open roles. Resolve by domain, slug, URL, or ID, and find similar companies.

  • Search8 endpoints

    Search posts by keyword or hashtag and resolve the identifiers that filter the rest of the API: locations, industries, schools, and service categories.

  • Jobs2 endpoints

    Search job listings by keyword, location, experience level, and posting recency, then read the detail behind a listing.

  • Posts6 endpoints

    Retrieve post details, comments, and reactions from a public post URL or slug.

  • Email3 endpoints

    Verify whether an email address can receive mail, find a person's address from a name and domain, or check a domain against the disposable-domain list for free.

  • Websites3 endpoints

    Fetch a public page's HTML or visible text, or discover published email addresses with source URLs. Email discovery checks up to eight pages and stops when a page yields addresses.

You do not need a LinkedIn account, a partner application, or browser automation. You need an API key and an HTTP client.

Why it exists

Why we built an independent LinkedIn data API

LinkedIn's official APIs are built for LinkedIn's partners. Most teams are not LinkedIn partners.

Official LinkedIn products

  • Sign-in and basic profile data for authenticated members
  • Marketing Developer Platform, for advertising workflows
  • Sales Navigator and Recruiter integrations, for approved partners
  • Access scoped by application review, use case, and business line

EnvoAPI

  • Public professional data, with an API key
  • One JSON shape across all 58 endpoints
  • No partner application, no approval queue
  • The credit cost of each call is returned in the response

If you have tried to get LinkedIn data into your own software, you know the problem. The official APIs are scoped to specific products: sign-in, advertising, and partner integrations for Sales Navigator and Recruiter. Access depends on an application review and an approved use case. A product team that wants to fill a CRM record, check a company's headcount, or watch a company's job postings usually does not qualify.

EnvoAPI exists for that team. It reads public professional pages and returns the data as structured JSON, with documented fields, predictable paging, and a published price per call. You sign up, create a key, and make your first request in a few minutes. EnvoAPI is an independent product. It is not an official LinkedIn API, it is not part of the LinkedIn Partner Program, and it is not affiliated with or endorsed by LinkedIn. We say so plainly because it matters for your compliance review.

Who it's for

Who uses EnvoAPI

Teams that need professional data inside software, without a manual research step in the middle.

  • Product and platform engineers

    You are adding enrichment to a SaaS product, an internal tool, or a data pipeline. You want a documented REST API, SDKs in Python, TypeScript, and Go, an OpenAPI definition, and errors you can handle in code.

  • Sales, marketing, and RevOps teams

    You want complete account and contact records in your CRM: job title, company, headcount, industry, and a verified work email. You run enrichment on signup, on import, or on a schedule.

  • Recruiting and talent teams

    You want a candidate's full experience, education, skills, and certifications from a profile URL, and a company's open jobs to see where it is hiring.

  • Research, data, and analyst teams

    You build company lists by industry, location, and size, then pull profiles, posts, and jobs into a warehouse and keep them current with stable IDs.

  • Automation builders and AI-assistant users

    You work in n8n, Make, Zapier, or Clay, or you want your assistant to look up a company mid-conversation through our MCP server. Same data, same credits, no code.

The API

How the API responds

Every endpoint follows the same rules, so you write your client once.

Authentication
A bearer API key in the Authorization header. There is one key format, and every key on an account has the same access.
The envelope
data holds the record. meta.creditCost tells you what the call cost. Lists page through meta.paging, with hasMore and a nextCursor, nextOffset, or nextStart.
Headers
Every response carries X-Request-Id for support, X-Credits-Remaining for your balance, and X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset so you can slow down before we make you.
Errors
A code such as invalid_request, resource_not_found, insufficient_credits, or rate_limit_exceeded, a readable message, and a retryable flag, so your client knows whether to try again.
Caching
Responses are sent with Cache-Control: private, no-store, so nothing sits in a shared cache between the data and your application.
GET/v1/companies/details/by-slugbash
curl -G "https://api.envoapi.com/v1/companies/details/by-slug" \  -H "Authorization: Bearer $ENVO_API_KEY" \  --data-urlencode "slug=northstar-systems"
Response200trimmed, synthetic companyjson
{  "data": {    "publicId": "company_4dm8z2",    "name": "Northstar Systems",    "slug": "northstar-systems",    "websiteUrl": "https://northstar.com",    "primaryIndustry": {      "publicId": "industry_4",      "name": "Software Development"    },    "employeeCount": 148,    "employeeCountRange": { "start": 51, "end": 200 }  },  "meta": {    "creditCost": 1  }}

Pricing

How pricing works

You pay in credits, not seats. The cost of a call is in the response, and the current cost of every endpoint is in the API reference.

  • 1credit for a company lookup
  • 2credits to verify an email
  • 10credits to find an email
  • 0credits for a disposable-domain check

Start with 100 free credits and no card. Paid plans start with Launch at $49/month for 10,000 credits and 60 requests per minute. Unused top-up credits carry over. Enterprise adds custom volumes, a service-level agreement, and a data processing agreement. See pricing for every plan.

Ways to use it

Use it from code, no-code tools, or an AI assistant

The same data, credits, and rate limits behind every route in.

  • SDKs

    Python, TypeScript, and Go. All three are MIT-licensed and live in one GitHub repository.

    View the SDKs

  • MCP server

    Connect your AI assistant to api.envoapi.com/mcp over streamable HTTP with OAuth or an API key. It is read-only and shares your credits and rate limits with REST.

    Set up MCP

  • Automation tools

    Call the API from the HTTP step in n8n, Make, Zapier, Pipedream, Power Automate, Workato, Retool, or Clay.

    Read the guides

Boundaries

Public data, handled carefully

EnvoAPI works with public professional data. It authenticates you with an API key only. It never asks for a LinkedIn login and does not use member accounts.

Public data can still be personal data. Before you put it into production, check your legal basis, your outreach rules, and the platform terms that apply to you. Our Trust page sets out who holds which role under GDPR and CCPA/CPRA, our retention periods, opt-out and suppression, security measures, international transfers, and the Responsible Use Policy. Each item links to the clause in the Terms or the Privacy Policy that binds us. We hold no third-party certifications today, and the page says so.

Principles

How we work

Four rules we hold the product to.

Say what it is
Public professional data, independent of LinkedIn, with the limits stated up front and the disclaimer on every page that needs it.
Return data you can keep
Documented fields, a stable ID on every profile and company so you can refresh a record later, and the same data and meta envelope on every endpoint.
Show the price in the response
Every successful call returns meta.creditCost. A request rejected as invalid, including one with an expired cursor, returns a 400 and costs nothing.
Contracts first
Every endpoint is defined in a versioned OpenAPI contract with examples, checked for drift. This site reads its endpoint counts from that same contract, so the numbers here match the API.

The team

Who builds EnvoAPI

EnvoAPI is built by a team of engineers focused on APIs and structured data. We work on three things: keeping the data model stable as the sources change, keeping the API reference accurate, and helping the people who are integrating.

If something does not work the way the reference says it should, write to [email protected].

FAQ

Questions about EnvoAPI

Is EnvoAPI affiliated with LinkedIn?

No. EnvoAPI is an independent product. It is not an official LinkedIn API, it is not part of the LinkedIn Partner Program, and LinkedIn does not endorse it.

Does EnvoAPI need my LinkedIn login?

No. Requests are authenticated with an EnvoAPI API key sent as a bearer token. You never share a LinkedIn login or connect a member account.

Am I charged for failed requests?

A request rejected as invalid, including one with an expired cursor, returns a 400 and no credits are charged. Rate limit and temporary capacity errors are marked retryable, so your client knows it can try again.

Can I use EnvoAPI without writing code?

Yes. Connect it to your AI assistant through the MCP server, or call it from the HTTP step in n8n, Make, Zapier, Clay, and similar tools.

Do you offer an SLA or a data processing agreement?

Enterprise plans include a service-level agreement (SLA) and a data processing agreement (DPA). The Trust page lists the data-handling terms that apply to every customer.

How do I reach a person?

Write to [email protected] or use the contact page. Questions about an integration, a bill, or a privacy review all go to the same place.

Evaluate us

Evaluate EnvoAPI before you commit

Read the API reference: 58 endpoints with parameters, schemas, and sample responses. Make real calls from the dashboard playground with your free credits. Check the status page for measured latency and incident history, each with the window it covers. Read the Trust page if you are running a procurement or privacy review.

Start building

Start with 100 free credits

Create a key, make a request, and look at the response before you pay for anything.

Get API keyView API documentation

100 free credits · No credit card required · 58 documented endpoints