LinkedIn API docs

LinkedIn API: Jobs — By query

Discover Jobs data on LinkedIn from a user query and connect the results to search, catalog, or research interfaces.

Use “By query” when an exact object ID is not known and relevant candidates must be found first.

Method GET
Entity Jobs
Versions 2
What this endpoint does

What you can build with this API method

Review the result and common workflows first, then move to parameters and a working request example.

What this endpoint helps with

The response includes matching Jobs, public context, and pagination data when more results are available.

When to use it

Use “By query” when an exact object ID is not known and relevant candidates must be found first.

Common use cases

In-product search

Add LinkedIn data search to customer-facing and internal interfaces.

Catalog building

Find candidates by query and save relevant objects for later enrichment.

Market research

Collect result sets for topic, creator, and competitive analysis.

Available versions

Response version

Both versions solve the same job and accept the same parameters. Use the switch to compare the response structure and choose the version your client expects.

Response version V2

Switch versions on this page to compare response structures while keeping the same documentation URL.

What stays the same

Authentication, required parameters, and the request shape stay the same across V1 and V2. In practice, you choose the version when you build the endpoint path and when you parse the response.

What changes between versions

The main difference is the response envelope. Use V2 for new integrations and keep V1 only when you need compatibility with an existing client contract.

How to use it

How to call the method

Use the same API key header and the same query parameters for both versions. This documentation shows the shared parameter set first, then version-specific endpoint paths and code snippets.

Input parameters

Shared parameters
Parameter Required Type Example Description
query Yes str value User-entered search query.
cursor No str | None QVFB... Next-page cursor returned by the previous response. Omit it for the first page.
location No str | None value Optional location text used by LinkedIn public jobs search. Example: United States.

Version-specific request path

V2

Choose a version when you copy the exact endpoint path, example URL, and code snippet. The parameter list above stays the same.

GET /api/v2/linkedin.com/jobs/by-query

Normalized format

Code examples

curl --request GET \
  --url "https://www.scrapestorm.net/api/v2/linkedin.com/jobs/by-query" \
  --header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
  --get --data-urlencode 'query=value' \
  # Optional parameters:
  # --data-urlencode 'cursor=QVFB...'
  # --data-urlencode 'location=value'
Response example

Live response by version

The preview keeps key fields and the first collection items so you can scan the response shape quickly. Switching versions changes the JSON format.

Response example

V2 response JSON

Verified example

This compact JSON example comes from the latest successful verification run for V2.

{
  "success": true,
  "status": "ok",
  "pagination": {
    "cursor": "10",
    "has_more": true
  },
  "search_context": {
    "query": "software",
    "location": "United States"
  },
  "data": {
    "jobs": {
      "count": 10,
      "items": [
        {
          "job_id": "4442141976",
          "title": "Software Engineer",
          "url": "https://www.linkedin.com/jobs/view/4442141976/",
          "company_name": "Infinite Computer Solutions",
          "company_url": "https://www.linkedin.com/company/infinite-computer-solutions",
          "company_username": "infinite-computer-solutions",
          "thumbnail_url": "https://example.com/image.jpg",
          "location": "New Jersey, United States",
          "posted_date": "2026-07-17",
          "posted_time_text": "2 days ago"
        },
        {
          "job_id": "4439496395",
          "title": "Software Engineer",
          "url": "https://www.linkedin.com/jobs/view/4439496395/",
          "company_name": "Forge",
          "company_url": "https://www.linkedin.com/company/forgehq",
          "company_username": "forgehq",
          "thumbnail_url": "https://example.com/image.jpg",
          "location": "New York, NY",
          "posted_date": "2026-07-14",
          "posted_time_text": "5 days ago"
        },
        {
          "_more_items": 8
        }
      ]
    }
  }
}
What to do next

Continue the evaluation

Use this documentation as the first decision point, then move into pricing, platform coverage, and integration rules before you connect the endpoint for recurring use.

Open the LinkedIn platform page

Compare adjacent entities, API method groups, and related docs before implementation.

Open platform page

Compare API method pricing

Check where this API method sits inside the public price table before you scale usage.

View pricing

Review integration rules

Use the starter docs to confirm authentication, versioning, retries, and mock vs live behavior.

Open docs
FAQ

Questions teams ask before implementation

Use these answers to decide whether this API method fits your workflow, versioning choice, and rollout plan.

What data does this LinkedIn API method return?

The method performs “By query” for Jobs. The compact response example below shows the exact field structure.

Should I choose V1 or V2?

Choose V2 for new integrations because it provides a normalized structure. Use V1 only for compatibility with clients that already consume the platform-native format.

What do I need for the first request?

Create an API key, send it in the request header, and provide the required parameters from the table. The code samples already contain the correct path and request structure.