Facebook Pixel
APILinkedIn Search

Search LinkedIn people (alias)

Alias endpoint for /search/people. Search for LinkedIn members/professionals with extensive filtering options. Ideal for recruiting, sales prospecting, and networking. Filter by name, job title, company, location, connection degree, and more. Recommended: For `connectionOf` or `followerOf` filters, prefer `search-people-v2` which natively supports these filters and returns more accurate results.

POST/people/search
Authentication requiredSearch

Code Examples

curl -X POST 'https://api.connectsafely.ai/linkedin/people/search' \
-H 'Authorization: Bearer <your_api_key>' \
-H 'Content-Type: application/json' \
-d '{"accountId":"acc_12345","keywords":"","count":25,"start":0,"filters":{"firstName":"example_value","lastName":"example_value","title":"Senior Developer","company":"Acme Inc","school":"example_value","locationId":"106981407","geoUrn":"106981407","industry":["Technology"],"connectionDegree":["example_value"],"currentCompanyIds":["Acme Inc"],"pastCompanyIds":["Acme Inc"],"schoolIds":["12345"],"profileLanguage":["example_value"],"serviceCategories":["example_value"],"openToVolunteer":false,"connectionOf":["example_value"],"followerOf":["example_value"]}}'

Alias endpoint for /search/people. Search for LinkedIn members/professionals with extensive filtering options. Ideal for recruiting, sales prospecting, and networking. Filter by name, job title, company, location, connection degree, and more.

Recommended: For connectionOf or followerOf filters, prefer search-people-v2 which natively supports these filters and returns more accurate results.

Parameters

No parameters.

Request Body

FieldTypeRequiredDescription
accountIdstringNoLinkedIn account ID to use for the search. If not provided, uses the default account.
keywordsstringNoSearch keywords for name, title, company, or skills
countnumberNoNumber of results to return per page
startnumberNoPagination offset (0-indexed)
filtersobjectNoOptional filters to narrow down search results

Example

{
  "accountId": "acc_12345",
  "keywords": "",
  "count": 25,
  "start": 0,
  "filters": {
    "firstName": "example_value",
    "lastName": "example_value",
    "title": "Senior Developer",
    "company": "Acme Inc",
    "school": "example_value",
    "locationId": "106981407",
    "geoUrn": "106981407",
    "industry": [
      "Technology"
    ],
    "connectionDegree": [
      "example_value"
    ],
    "currentCompanyIds": [
      "Acme Inc"
    ],
    "pastCompanyIds": [
      "Acme Inc"
    ],
    "schoolIds": [
      "12345"
    ],
    "profileLanguage": [
      "example_value"
    ],
    "serviceCategories": [
      "example_value"
    ],
    "openToVolunteer": false,
    "connectionOf": [
      "example_value"
    ],
    "followerOf": [
      "example_value"
    ]
  }
}

Responses

StatusDescription
200People retrieved successfully

200 Response Parameters

NameTypeDescription
successboolean
peoplearray
totalResultsnumber

200 Example

{
  "success": true,
  "people": [],
  "totalResults": 0
}

Search LinkedIn people (V2 - with auto-pagination)

Search for LinkedIn members with enhanced filtering options and automatic pagination. Supports additional filters like connectionOf, followerOf, and schoolIds. Automatically handles LinkedIn page-based pagination internally - specify the total count you want and the API will fetch multiple pages as needed (max 10 pages, ~10 results per page). Better for finding people connected to specific profiles or following specific accounts. Important: This V2 endpoint uses LinkedIn's newer search, which is rolling out gradually by region. If this endpoint does not return results for your account, use the V1 `/search/people` endpoint instead. Rate limit: 1,000 search calls per account per day (resets at midnight UTC), and 30 calls per minute. Pagination is billed per page walked, so a `count` of 25 spends about 3 calls. Separately, LinkedIn applies its own commercial use limit to people search: roughly 100 searches a month on a free account, ~300 on Premium Career, ~500 on Premium Business, and effectively unlimited with Sales Navigator. That ceiling belongs to LinkedIn, is computed from search and browsing history rather than published, resets on the 1st of the month, and is not enforced or reported by this API. Maximum 1000 results per search.

Search LinkedIn jobs

Search for job postings on LinkedIn with various filters. Supports pagination and multiple filter criteria including location, employment type, experience level, and more. Filters changed when LinkedIn rebuilt its job search. `industry`, `locationId`, `geoUrn` and `jobType` are rejected with a 400 rather than ignored — LinkedIn no longer offers those filters. Use `employmentType`, `experienceLevel`, `geoId`, and `segmentIds` (filter-pill ids, e.g. `"225001:272001"` for Remote). | Old filter | Use instead | | --- | --- | | `jobType: ["F"]` | `employmentType: ["full-time"]` | | `experienceLevel: ["4","5","6"]` | `experienceLevel: ["senior","director","executive"]` | | `workplaceType: ["2"]` (Remote) | `workplaceType: ["remote"]` | | `industry` | `segmentIds` (the ids LinkedIn offers vary by keyword) | | `locationId` / `geoUrn` | `geoId` | `workplaceType` is applied to the returned cards, not by LinkedIn. LinkedIn honours the Remote segment, but when the fully-filtered pool is thin it BACKFILLS the page with rows that do not match and still answers 200. Measured on one account with keywords "VP of Marketing" and the Remote segment held constant: alone 10/10 remote, plus `experienceLevel` 9/10, plus `past-month` 8/10, plus `past-week` 5/10, plus `past-24h` 5/10, plus `past-24h` and `experienceLevel` 4/10. It tracks how narrow the filter set is, not the keyword, so no segment id avoids it. Filtering on each card's own pill is therefore the only reliable option, with two consequences: a page may return fewer than `count` rows (check `hasMore` and page on), and jobs LinkedIn labels with no workplace pill are excluded rather than assumed. Rate limit: 1,000 search calls per account per day (resets at midnight UTC), and 30 calls per minute. One request counts as one call regardless of `count`.

On this page