LinkedIn Profile Search

Search for LinkedIn profiles by keyword with optional location and job-title filters. The request takes a search query. Use it for account discovery and creator research. The POST request schema also lists fields, max_items. Use the results to organize a research workflow and cross-check the relevant source records.

Selected price
$0.088 base + $0.0044 / result Published pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Search query for LinkedIn profiles: a role, name, or keywords (e.g. 'Marketing Manager').
Optional parameters (37)
Optional. Comma-separated keys (dotted paths like `author.name` descend into nested objects) to keep on each result item: each row of the API's result list, or the `data` object itself for an API that returns one record. Keys are matched relative to that item, not against the top-level response envelope, so use `jq` to reshape the whole envelope. Shrinks the response without changing cost.
Optional. Cap the number of result rows returned; a `_truncated` note reports how many were withheld so you can page via the API's own `limit`. An API that returns one record is not trimmed. Does not change cost.
Optional. Return only a structural outline (top-level keys, item counts, and per-field byte sizes) instead of the full data. Does not change cost.
Optional. A jq expression applied to the result envelope; its output replaces `output` (multiple outputs collect into an array). Reshape freely, e.g. `jq=.data | {title, description, md: .markdown[:3500]}`. Runs sandboxed with a 250ms / 2MB budget; on failure the full result is returned with a `jqError`. Does not change cost.
Optional. The most you are willing to pay for this one request, in US dollars (for example 0.05). Any route that would charge more than this is not used, so a request only ever runs on something you can afford. If nothing is available at or below your amount, the request is refused before it runs, nothing is charged, and the message tells you the cheapest price per request so you can raise it. Leave it out to accept the normal price.
Optional wallet idempotency key, scoped to this customer for 24 hours. When the gateway honors the key, this synchronous in-process execution can continue after the caller disconnects, bounded by its execution deadline. A completed replayable result charges normally exactly once and can be replayed without another provider run or charge. A pending duplicate returns 409 idempotency_in_progress; reuse with different request semantics returns 409 idempotency_conflict.
Optional, default true. When false, only the sources listed in `source` may serve; the request is refused with no charge if none of them can. When true, the listed sources are tried first and any other source may serve after them, at the normal price.
companyHeadcount array
Filter by current company size (employee count). Codes: A=Self-Employed, B=1-10, C=11-50, D=51-200, E=201-500, F=501-1,000, G=1,001-5,000, H=5,001-10,000, I=10,001+.
companyHeadquarterLocations array
Filter by the location of the person's current company headquarters, by place name (e.g. ['United States']).
currentCompanies array
Filter to people who currently work at any of these companies, by name (e.g. ['Google','Meta']). Multiple names widen the match (OR).
excludeCompanyHeadquarterLocations array
Exclude people whose current company is headquartered in any of these locations.
excludeCurrentCompanies array
Exclude people who currently work at any of these companies, by name.
excludeCurrentJobTitles array
Exclude people whose current job title matches any of these.
excludeFunctionIds array
Exclude these job functions (same codes as functionIds).
excludeLocations array
Exclude people in any of these locations, by place name.
excludePastCompanies array
Exclude people who previously worked at any of these companies, by name.
excludePastJobTitles array
Exclude people who held any of these past job titles.
excludeSchools array
Exclude people who attended any of these schools, by name.
excludeSeniorityLevelIds array
Exclude these seniority levels (same codes as seniorityLevelIds).
firstNames array
Filter to people whose first name matches any of these.
functionIds array
Filter by job function. Codes: 1=Accounting, 2=Administrative, 3=Arts and Design, 4=Business Development, 5=Community and Social Services, 6=Consulting, 7=Education, 8=Engineering, 9=Entrepreneurship, 10=Finance, 11=Healthcare Services, 12=Human Resources, 13=Information Technology, 14=Legal, 15=Marketing, 16=Media and Communication, 17=Military and Protective Services, 18=Operations, 19=Product Management, 20=Program and Project Management, 21=Purchasing, 22=Quality Assurance, 23=Real Estate, 24=Research, 25=Sales, 26=Customer Success and Support.
ignoreSources array
Optional. Source ids to skip for this request, taken from this endpoint's `lanes[].source.id`. The cheapest remaining source serves and the price is that of the dearest remaining source. An id that does not serve this endpoint, or that is also in `source`, is rejected as invalid input with no charge; skipping every source is rejected the same way.
Optional current job title filter (e.g. 'Software Engineer').
lastNames array
Filter to people whose last name matches any of these.
Maximum number of full profiles to return (1-25, default 10). You are billed per profile returned, so a lower limit costs less.
Optional location filter (e.g. 'San Francisco').
pastCompanies array
Filter to people who previously worked at any of these companies, by name.
pastJobTitles array
Filter by a past job title the person held (e.g. ['Product Manager']).
Optional; omit it and routing is unchanged, with the cheapest source serving. Prefer sources whose typical response time (median over the trailing 30 days, as published on this endpoint's lane health) is under this many milliseconds; among those, the cheapest serves. This can raise your price: when the cheapest source misses the target, a faster and dearer one serves, and you are quoted and charged its price. If no source is that fast the request is still served, by whichever source offers the best speed for its price - it is never refused for being slow. Sources we have not timed are tried last. This is a preference, not a guarantee: the median describes past requests and is not a ceiling on this one, and it excludes any wait this request itself asks for. On a paginated walk it applies to the first page only: later pages stay with the source that page chose, at the price it was quoted.
profileLanguages array
Filter by the profile's primary language.
When true, only return people who recently changed jobs (a strong sales/recruiting signal).
When true, only return people who recently posted on LinkedIn (an activity signal).
schools array
Filter to people who attended any of these schools, by name.
seniorityLevelIds array
Filter by seniority level. Codes: 100=In Training, 110=Entry Level, 120=Senior, 130=Strategic, 200=Entry Level Manager, 210=Experienced Manager, 220=Director, 300=Vice President, 310=CXO, 320=Owner/Partner.
source array
Optional. Source ids to prefer, in order, taken from this endpoint's `lanes[].source.id` in /catalog or /apis. Omit it and the cheapest source serves, with automatic failover. Listed sources are tried first in the order given, then the others, unless `allowFallbacks` is false. A single source with `allowFallbacks` false is served only by that source at its price, quoted and charged exactly, with no failover. The price is that of the dearest source that may serve. An id that does not serve this endpoint is rejected as invalid input with no charge; a listed source that is not serving right now is refused with no charge, so omit `source` to be served by another. On a paginated walk, later pages must include the source that served page one, or omit `source`.
yearsAtCurrentCompanyIds array
Filter by tenure at the current company. Codes: 1=Less than 1 year, 2=1 to 2 years, 3=3 to 5 years, 4=6 to 10 years, 5=More than 10 years.
yearsOfExperienceIds array
Filter by total years of experience. Codes: 1=Less than 1 year, 2=1 to 2 years, 3=3 to 5 years, 4=6 to 10 years, 5=More than 10 years.

Sample response

{
  "output": {
    "data": {
      "items": [
        {
          "about": "20 years scaling B2B SaaS revenue teams from seed to IPO. Currently building out the commercial segment at Salesforce.",
          "experience": [
            {
              "company": "Salesforce",
              "endDate": "Present",
              "location": "Chicago, Illinois",
              "startDate": "Jan 2023",
              "title": "VP of Sales, Commercial"
            },
            {
              "company": "Salesforce",
              "endDate": "Dec 2022",
              "location": "Chicago, Illinois",
              "startDate": "Jun 2019",
              "title": "Senior Director of Sales"
            }
          ],
          "firstName": "Marcus",
          "handle": "marcus-chen-sales",
          "headline": "VP of Sales, Commercial at Salesforce",
          "id": "ACoAAAvpsales001",
          "image": "https://media.licdn.com/dms/image/D4E03AQMarcusChenProfile/profile-displayphoto-shrink_800_800/0/1701000000007?e=1735689600",
          "lastName": "Chen",
          "location": "Chicago, Illinois, United States",
          "url": "https://www.linkedin.com/in/marcus-chen-sales"
        },
        {
          "about": "Leading HubSpot's EMEA sales org across mid-market and enterprise segments.",
          "experience": [
            {
              "company": "HubSpot",
              "endDate": "Present",
              "location": "Dublin, Ireland",
              "startDate": "Apr 2021",
              "title": "VP of Sales, EMEA"
            }
          ],
          "firstName": "Renee",
          "handle": "renee-okafor-hubspot",
          "headline": "VP of Sales, EMEA at HubSpot",
          "id": "ACoAAAvpsales002",
          "image": "https://media.licdn.com/dms/image/D4E03AQReneeOkaforProfile/profile-displayphoto-shrink_800_800/0/1701000000009?e=1735689600",
          "lastName": "Okafor",
          "location": "Dublin, Ireland",
          "url": "https://www.linkedin.com/in/renee-okafor-hubspot"
        }
      ]
    },
    "found": true
  }
}

Response result

Response structure

Inferred from examples
  • outputobject
    • dataobject
      • itemsobject[]
        • aboutstring
        • experienceobject[]
          • companystring
          • endDatestring
          • locationstring
          • startDatestring
          • titlestring
        • firstNamestring
        • handlestring
        • headlinestring
        • idstring
        • imagestring
        • lastNamestring
        • locationstring
        • urlstring
    • foundboolean

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use LinkedIn Profile Search with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.