LinkedIn Search Jobs API

LinkedIn Search Jobs

Features

• Location-led discoveryStart every query with a non-empty location and optionally narrow the public listing sample with a keyword, country, company, or other provider filter.
• Flexible source filtersForward time_range, job_type, experience_level, remote, company, location_radius, selective_search, and exclusion values without inventing SocQ enums.
• Configurable result capSet results_limit from 1 through 2000 for the single discovery query; the default is 100 and the provider may return fewer records.
• Canonical job recordsReceive stable job, company, location, salary, publication, expiry, and collection fields rather than provider-specific nesting.
• Nullable source fidelityKeep unavailable salary, remote, company, experience, location, publication, and expiry values null instead of inferring them.

Parameters

How to Use

Submit one location-based query, poll the asynchronous task, and process every returned result page.

1. Choose a required location and add only provider filter values whose interpretation you have tested.
2. POST the query to /v1/linkedin/search-jobs and save the returned task_id.
3. Poll /v1/tasks/{task_id} until the task reaches a terminal status.
4. On success, process data.results.items and follow next_cursor whenever has_more is true.

curl -X POST "https://api.socq.ai/v1/linkedin/search-jobs" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"location":"Seattle","keyword":"Python","country":"US","results_limit":20}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is true

Best Use Cases

• Regional role discovery: Collect public listings for a consistent role-and-location query and retain the collection time for later comparison.
• Employer and role review: Inspect which employers, titles, places, work modes, experience levels, and employment types appear in the returned sample.
• Compensation availability: Identify listings that expose salary information while preserving missing compensation as an explicit null.
• Job workflow intake: Feed normalized public listing URLs and fields into review, deduplication, alerting, or downstream analysis workflows.

Pro Tips

• Test provider-specific filter spellings on a small query before using them in a recurring workflow.
• Use the same filters and collection schedule when comparing locations or dates.
• Deduplicate by stable job id or listing URL because renewed and overlapping searches can surface the same opening.
• Treat remote labels as source signals and read the description for geographic, residency, or time-zone constraints.
• Keep published_at, expires_at, and collected_at distinct so listing time is not confused with retrieval time.
• Treat empty results as one collection outcome, not proof that no matching public jobs exist.

Related APIs