linkedin-jobs

The job cards of LinkedIn's public jobs search, one row per card: title, company, location, when it was posted (LinkedIn's relative text and the date), the job's link, its id, and the salary when the card shows one. query is the search; location a place or Remote; posted keeps the last day, week or month; start is LinkedIn's offset (a page holds up to 60 cards, LinkedIn moves 25 a step, up to 975); limit caps the rows. Fetched through a home address in the US, about 3 to 8 s. No login: this is what LinkedIn shows a visitor.

stagedlinkedin.comWASM module8 fields2 units · a browser on an exitfresh 15 min
‹ Recipes
…json
POST api.crawl4ai.com/recipes/…

$ crawl recipe

              
Live · your key · counts against your quota✓ 200 OK
# Hit Run - the rows render here as a table, with the cost

Fields

8 columns on every row. null means the site does not state it.
fieldtypemeaning
titlestring
companystring
locationstring
postedstring
posted_onstring
urlstring
job_idstring
salary

null means the site does not state it.

titlestring
companystring
locationstring
postedstring
posted_onstring
urlstring
job_idstring
salary

How it behaves

Cost. 2 units · a browser on an exit. A failed run costs 0.

Freshness 15 min. The same input within 15 min is served from cache at 0 units.

Questions about this recipeQuestions

Short answers. The API reference has the long ones.

Call POST /recipes/linkedin-jobs with your key and query and location and posted. You get rows with the 8 fields above. The recipe is tested against the live site every 6 hours.

Need more from LinkedIn?

Extra fields, higher volume, or a private copy with a freshness SLA. We build it on Enterprise.

Request a change

For developers

Get a free API key and run your first crawl.

1,000 credits every month. No credit card. Your self-hosted setup keeps working.

For teams

Talk to us about volume, regions and an SLA.

A 30-minute call with the team that writes the crawler. DPA on request, invoice billing, your choice of US, EU or Singapore.