LinkedIn Search API for People, Companies, Jobs and Posts

• 1 routePeopleKeywords + profile filtersdata.profiles
• 2 routesCompaniesKeywords or a website domaindata.companies
• 1 routeJobsKeywords + hiring filtersdata.jobs
• 2 routesPostsKeywords or a hashtagdata.posts

1read -r -s -p "EnvoAPI key: " ENVO_API_KEY2export ENVO_API_KEY

The authentication guide covers key handling. For lookups and data beyond search, explore the LinkedIn data API.

1curl --fail-with-body --get 'https://api.envoapi.com/v1/jobs/search' \2  --header "Authorization: Bearer $ENVO_API_KEY" \3  --header 'Accept: application/json' \4  --data-urlencode 'keywords=software engineer' \5  --data-urlencode 'start=0' \6  --data-urlencode 'location=geo_6yITcz' \7  --data-urlencode 'sort=relevance' \8  --data-urlencode 'timePosted=any'

1{2  "data": {3    "jobs": [4      {5        "title": "Software Engineer",6        "url": "https://www.linkedin.com/jobs/view/1234567890/",7        "location": null,8        "postedAt": null,9        "companyName": "Example Systems",10        "companyUrl": "https://www.linkedin.com/company/example-systems/",11        "companyLogoUrl": null,12        "isPromoted": false,13        "isEasyApply": true14      }15    ]16  },17  "meta": {18    "paging": {19      "start": 0,20      "count": 10,21      "hasMore": true22    },23    "creditCost": 124  }25}

The job search reference defines filters. Check the job search pagination schema and our guide to job details and company hiring workflows for pagination and next steps.

For filter pickers, typeahead and enrichment, see how to build search and filtering into your application.

1. 01

   Build a people search experience

   Show each person's name, headline and available location. Keep the returned LinkedIn URL for a subsequent lookup; hide missing optional fields. For company results, show the name, available logo and summary, then offer a clear action to view or enrich the selected account.

   ExampleNode.js backend adapter for people and location search

   Add Express and Zod to your Node.js application. Save this example as server.mjs and run node server.mjs with ENVO_API_KEYset on the server. Route your frontend's /api/search requests to this backend. It validates inputs and the response fields used by the UI, forwards rate limit errors and makes no automatic retries.

   1import express from "express";2import { z } from "zod";34const app = express();5const key = process.env.ENVO_API_KEY;6if (!key) throw new Error("Set ENVO_API_KEY on the server.");78const peopleInput = z.object({9  q: z.string().trim().min(1).max(200),10  location: z.string().trim().min(1).max(200).optional(),11  offset: z.coerce.number().int().min(0).max(50).default(0),12});13const locationInput = z.object({14  q: z.string().trim().min(2).max(200),15});16const peopleResponse = z.object({17  data: z.object({18    profiles: z.array(z.object({19      name: z.string(),20      headline: z.string().nullable(),21      location: z.string().nullable(),22      linkedinUrl: z.string().nullable(),23    })),24  }),25  meta: z.object({26    paging: z.object({27      hasMore: z.boolean(),28      nextOffset: z.number().nullable(),29    }),30  }),31});32const locationResponse = z.object({33  data: z.object({34    locations: z.array(z.object({ id: z.string(), name: z.string() })),35  }),36});3738async function callEnvo(path, params, schema, res) {39  const response = await fetch("https://api.envoapi.com" + path + "?" + params, {40    headers: { Authorization: "Bearer " + key, Accept: "application/json" },41    signal: AbortSignal.timeout(15000),42  });43  if (!response.ok) {44    const retryAfter = response.headers.get("Retry-After");45    if (retryAfter) res.set("Retry-After", retryAfter);46    res.status(response.status).json({ error: "Search request failed." });47    return null;48  }49  return schema.parse(await response.json());50}5152// Mount these routes behind your application's authentication and rate limits.53app.get("/api/search/people", async (req, res) => {54  const input = peopleInput.safeParse(req.query);55  if (!input.success) return res.status(400).json({ error: "Invalid search." });56  const { q, location, offset } = input.data;57  const params = new URLSearchParams({ keywords: q, offset: String(offset) });58  if (location) params.set("location", location);59  try {60    const payload = await callEnvo("/v1/profiles/search", params, peopleResponse, res);61    if (!payload) return;62    res.json({ people: payload.data.profiles, pagination: payload.meta.paging });63  } catch {64    res.status(502).json({ error: "Search is temporarily unavailable." });65  }66});6768app.get("/api/search/locations", async (req, res) => {69  const input = locationInput.safeParse(req.query);70  if (!input.success) return res.status(400).json({ error: "Invalid location query." });71  const params = new URLSearchParams({ keywords: input.data.q });72  try {73    const payload = await callEnvo("/v1/search/locations", params, locationResponse, res);74    if (!payload) return;75    res.json({ suggestions: payload.data.locations });76  } catch {77    res.status(502).json({ error: "Location suggestions are unavailable." });78  }79});8081app.listen(3001);

2. 02

   Add typeahead and dynamic filters

   Require at least two characters and debounce location suggestions by 300 ms. Cancel pending requests when the input changes, and ignore stale responses. When a user selects a suggestion, store its id as the search filter. Render selected filters as removable chips with a Clear all action; typing a new location clears the previous selection. Submit the full search when the user applies the query and filters.

   Location discovery uses /v1/search/locations with keywords and returns data.locations. Industry discovery uses /v1/search/industries with query and returns data.industries. Pass their resolved IDs into supported search filters.

   ExampleFrontend typeahead with debounce and request cancellation

   Connect the render, loading and error callbacks to your UI. Call input(value) on input changes and destroy() when unmounting. Render suggestions as accessible selectable options with keyboard support and use text nodes for API values.

   1type LocationSuggestion = { id: string; name: string };2type TypeaheadUI = {3  render: (suggestions: LocationSuggestion[]) => void;4  loading: (active: boolean) => void;5  error: (message: string) => void;6};78export function createLocationTypeahead(ui: TypeaheadUI) {9  let timer: ReturnType<typeof setTimeout> | undefined;10  let active: AbortController | undefined;1112  function cancel() {13    clearTimeout(timer);14    active?.abort();15    active = undefined;16    ui.loading(false);17  }1819  function input(value: string) {20    cancel();21    ui.render([]);22    ui.error("");23    const query = value.trim();24    if (query.length < 2) return;2526    timer = setTimeout(async () => {27      const controller = new AbortController();28      active = controller;29      ui.loading(true);30      try {31        const response = await fetch(32          "/api/search/locations?q=" + encodeURIComponent(query),33          { signal: controller.signal },34        );35        if (!response.ok) throw new Error("Location suggestions unavailable.");36        const result = await response.json();37        if (active === controller) ui.render(result.suggestions);38      } catch {39        if (active === controller) ui.error("Unable to load suggestions. Try again.");40      } finally {41        if (active === controller) {42          ui.loading(false);43          active = undefined;44        }45      }46    }, 300);47  }4849  return { input, destroy: cancel };50}

3. 03

   Handle pagination and UI states

   • Initial loading: show progress or result-card skeletons.
   • Loading more: retain existing results and disable duplicate requests.
   • No results: suggest broader keywords or fewer applied filters.
   • Request failed: show a retry action and retain the current results.
   • End of results: remove Load more when there is no valid next offset.

   For people search, use meta.paging.nextOffset while hasMoreis true, within the 0–50 offset range. Keep the submitted query and filters unchanged across pages. A new search resets the list and cancels the previous loader. On HTTP 429, respect the backend's Retry-After header before offering a retry.

   ExampleLoad more pagination with loading and error callbacks

   Create a loader for the submitted query and selected location ID. Call loadMore() for the first page and subsequent pages. Append returned cards in your UI and hide Load more when pagination reports no further page or its next offset exceeds 50.

   1type PeoplePage = {2  people: Array<{3    name: string;4    headline: string | null;5    location: string | null;6    linkedinUrl: string | null;7  }>;8  pagination: { hasMore: boolean; nextOffset: number | null };9};1011// Create a new loader for each submitted query and selected location ID.12// Call destroy() when replacing the search or unmounting the view.13export function createPeopleLoader(14  query: string,15  locationId: string | undefined,16  ui: {17    append: (page: PeoplePage) => void;18    loading: (active: boolean) => void;19    error: (message: string) => void;20  },21) {22  let offset: number | null = 0;23  let active: AbortController | undefined;24  let disposed = false;2526  async function loadMore() {27    if (disposed || active || offset === null) return;28    const controller = new AbortController();29    active = controller;30    ui.error("");31    ui.loading(true);32    const params = new URLSearchParams({ q: query, offset: String(offset) });33    if (locationId) params.set("location", locationId);34    try {35      const response = await fetch("/api/search/people?" + params, {36        signal: controller.signal,37      });38      if (!response.ok) throw new Error("Search request failed.");39      const page: PeoplePage = await response.json();40      if (disposed) return;41      ui.append(page);42      const next = page.pagination.nextOffset;43      offset = page.pagination.hasMore && next !== null && next > offset && next <= 5044        ? next : null;45    } catch {46      if (!disposed) ui.error("Unable to load results. Try again.");47    } finally {48      active = undefined;49      if (!disposed) ui.loading(false);50    }51  }5253  function destroy() {54    disposed = true;55    active?.abort();56    ui.loading(false);57  }5859  return { loadMore, destroy };60}

4. 04

   Search, refine and enrich selected records

   A sales user searches for Head of Sales, selects Singapore from location suggestions and compares the returned people cards. Opening a selected card triggers a profile detail lookup. If the workflow starts with target accounts, use company search first, then retrieve company details. Enrich records when a user opens or saves them, and offer downstream actions such as adding a record to a CRM or assigning it to a recruiter.

Get your free API key and try the route that fits your input.

• Official access

  Official LinkedIn access depends on the product, scopes and approval requirements. Some permissions are open, while other products require program access. Review the LinkedIn API access requirements for your integration.

• Job posting

  LinkedIn provides a Job Posting API for authorized partner integrations that publish and manage job listings. It serves job posting, rather than public job search. For public job cards through EnvoAPI, use /v1/jobs/search.

• Your responsibilities

  The LinkedIn User Agreement restricts automated collection. You are responsible for your use of returned data, including applicable privacy notices, lawful processing and data rights under GDPR, CCPA and other relevant laws.

Review our data responsibility and trust policies when designing your downstream workflow.