LinkedIn Job Search

Search for LinkedIn job listings by keywords and filters. Input fields and response shapes depend on the selected implementation. Use it in job-market research or vacancy tracking. Choose an implementation and check its published request fields, examples, and usage pricing before integrating.

Selected price
$0.001 / callPublished pricing
Sellers / implementations
2 / 2
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

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

Request parameters
Optional parameters (15)
Search jobs by title
Filter by company ID. One value or multiple comma-separated.
Filter by location text
Filter by location as LinkedIn Geo ID. Overrides the location query param. Use the /linkedin/geo-id-search endpoint to find the Geo ID
Sort by field. Supported values: 'relevance', 'date'
Filter by workplace type. One or multiple values comma-separated. Supported values: 'office', 'hybrid', 'remote'
Filter by employment type. One or multiple values comma-separated. Supported values: 'full-time', 'part-time', 'contract', 'temporary', 'internship'
Filter by salary range. Supported values: '40k+', '60k+', '80k+', '100k+', '120k+', '140k+', '160k+', '180k+', '200k+'
Filter posts by maximum posted date. Supported values: '24h', 'week', 'month'
Filter by experience level. One or multiple values comma-separated. Supported values: 'internship', 'entry', 'associate', 'mid-senior', 'director', 'executive'
Filter by industry ID. One value or multiple comma-separated industry IDs. Full list of IDs: https://github.com/HarvestAPI/linkedin-industry-codes-v2/blob/main/linkedin_industry_code_v2_all_eng.csv
Filter by job function ID. One value or multiple comma-separated function IDs. Full list of IDs: https://github.com/HarvestAPI/apify-linkedin-profile-search/blob/main/.actor/input_schema.json#L142
Include this parameter to filter jobs with under 10 applicants
Set this parameter to 'true' filter jobs with Easy Apply option or 'false' to exclude. Values can be 'true' or 'false'
Page number for pagination

Sample response

{
  "elements": [
    {
      "company": {
        "linkedinUrl": "<linkedinUrl>",
        "name": "<name>",
        "universalName": "<universalName>"
      },
      "easyApply": false,
      "id": "<id>",
      "location": {
        "linkedinText": "<linkedinText>"
      },
      "postedDate": "<postedDate>",
      "title": "<title>",
      "url": "<url>"
    }
  ],
  "error": "<error>",
  "pagination": {
    "pageNumber": 0,
    "pageSize": 0,
    "paginationToken": "<paginationToken>",
    "previousElements": 0,
    "totalElements": 0,
    "totalPages": 0
  },
  "query": {
    "companyId": "<companyId>",
    "geoId": "<geoId>",
    "location": "<location>",
    "page": 0,
    "postedLimit": "<postedLimit>",
    "sortBy": "<sortBy>",
    "title": "<title>",
    "workplaceType": "<workplaceType>"
  },
  "status": 0
}

Response result

Response structure

Inferred from examples
  • elementsobject[]
    • companyobject
      • linkedinUrlstring
      • namestring
      • universalNamestring
    • easyApplyboolean
    • idstring
    • locationobject
      • linkedinTextstring
    • postedDatestring
    • titlestring
    • urlstring
  • errorstring
  • paginationobject
    • pageNumberinteger
    • pageSizeinteger
    • paginationTokenstring
    • previousElementsinteger
    • totalElementsinteger
    • totalPagesinteger
  • queryobject
    • companyIdstring
    • geoIdstring
    • locationstring
    • pageinteger
    • postedLimitstring
    • sortBystring
    • titlestring
    • workplaceTypestring
  • statusinteger

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 Job Search with your agent

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