/linkedin/search/jobs

POST /api/linkedin/search/jobs

Price: 1 credit

Linkedin Search Jobs

How to use it

Search LinkedIn job listings by keywords, location, and filters. posted_within (day, week, month) keeps only jobs listed within the last 24 hours, 7 days or 30 days. sort=recent orders results by the listed date, newest first. The X-Total-Available-Results header is present when no more results exist for the query and absent when count cut the list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keywords string — Any keyword for searching in the job. For exact search put desired keywords into brackets (default: ""; examples: "python")
• sort string nullable — Job sorting type (one of: "recent", "relevant"; examples: "recent")
• experience_level array nullable — Job experience level (one of: "internship", "entry_level", "associate", "mid_senior", "director", "executive"; examples: ["internship","associate","mid_senior"])
• job_types array nullable — Job types (one of: "full_time", "part_time", "contract", "temporary", "internship", "other"; examples: ["full_time","contract"])
• work_types array nullable — Work types (one of: "on-site", "hybrid", "remote"; examples: ["hybrid","remote"])
• industry union — Industry URN or name. Valid top-level industries: Technology, Information and Media; Professional Services; Manufacturing; Hospitals and Health Care; Retail; Government Administration; Holding Companies; Oil, Gas, and Mining; Real Estate and Equipment Rental Services; Transportation, Logistics, Supply Chain and Storage; Utilities; Wholesale. Text auto-resolves to URN. (examples: ["industry:96"])
  • type string required (one of: "industry")
  • value string required
• company array nullable — Company URN, can be obtained in /linkedin/search/company, only company urn type is allowed (examples: ["company:1035"])
  • type string required (one of: "company")
  • value string required
• posted_within string nullable — Keep only jobs listed within the last 24 hours, 7 days or 30 days; applied before count (one of: "day", "week", "month"; examples: "week")
• location string — Job location (default: "worldwide"; examples: "Tokyo")
• count integer required — Max result count (max: 1000; >: 0)

Response

• @type string (default: "LinkedinSearchJob")
• urn object required
  • type string required (one of: "job")
  • value string required
• name string required
• url string required
• company object nullable
  • @type string (default: "LinkedinSearchJobCompany")
  • urn object required nullable
    • type string required (one of: "fsd_company", "company")
    • value string required
  • name string required
  • alias string required nullable
  • url string required nullable
  • image string nullable
• location string nullable
• work_type string nullable (one of: "on-site", "hybrid", "remote")
• created_at integer nullable
• is_promoted boolean (default: false)
• is_east_apply boolean (default: false)
• is_early_applicant boolean (default: false)
• applicant_count integer nullable — Parsed from the card's own applicant-count text, e.g. '17 applicants'.
• is_verified boolean — The card carries LinkedIn's verified-hiring badge. (default: false)
• relevance_insight string nullable — LinkedIn's own relevance line for the card, e.g. 'Actively reviewing applicants'.
• highlight string nullable — LinkedIn's own highlight line for the card: salary range, benefit count, specialty tag or shift, depending on the job.

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.