ApifyLinkedInSocial

LinkedIn job postings by title, company or location

apify.linkedin.search.jobs

Scrape LinkedIn job postings by title, company, location or filters — the hiring-signal search that also answers 'what is this company hiring for' via the company filter

Price
$0.001/resultZum Anbieterpreis
Success rate
100 %Last 30 days · 6.106 calls
Latency p50
6.5 sp95 41 s
Last verified
26.09.2026Verified working
POSThttps://toolswitch.dev/v1/tools/apify.linkedin.search.jobs?timeout=90&maxItems=1&maxTotalChargeUsd=0.05Preview
Try onlineDemnächstProvider docs ↗
  • Uses platform quota
  • Synchronous response
  • Reads public data

Parameter

only the declared body fields are accepted: geoIds is refused because the actor bills a start for each geo id it searches — name places in `locations` instead. The response is the dataset items array directly — no run envelope. Community actor scraping LinkedIn's public job search: no LinkedIn login needed, but expect the flakiness every LinkedIn scraper shows — retry before concluding a company has no openings

ParameterTypErforderlichBeschreibungBeispiel
Abfrageparameter
timeoutGanzzahlOptionaltreg's key requires 1-90 so the run and its rows arrive before any wait gives up (a larger pull needs your own key). seconds before the synchronous run is cut off; Apify closes the connection at 300s regardless90
maxItemsGanzzahlOptionaloptional row cap; pay-per-event actors that take the row count from their own input ignore it, so maxTotalChargeUsd is the spend limit25
maxTotalChargeUsdZahlOptionalthe spend cap Apify enforces on every event this run bills, in dollars. treg's key requires it, above 0 and at most 1, and holds it for the call0.5
  • Abfrageparameter
  • timeoutGanzzahlOptional

    treg's key requires 1-90 so the run and its rows arrive before any wait gives up (a larger pull needs your own key). seconds before the synchronous run is cut off; Apify closes the connection at 300s regardless

    Beispiel: 90

  • maxItemsGanzzahlOptional

    optional row cap; pay-per-event actors that take the row count from their own input ignore it, so maxTotalChargeUsd is the spend limit

    Beispiel: 25

  • maxTotalChargeUsdZahlOptional

    the spend cap Apify enforces on every event this run bills, in dollars. treg's key requires it, above 0 and at most 1, and holds it for the call

    Beispiel: 0.5

Codebeispiele

Ersetze $TOOLSWITCH_KEY durch den in der Konsole erstellten Schlüssel.

Preview
curl -X POST 'https://toolswitch.dev/v1/tools/apify.linkedin.search.jobs?timeout=90&maxItems=1&maxTotalChargeUsd=0.05' \
  -H "X-Toolswitch-Key: $TOOLSWITCH_KEY" \
  -H "Content-Type: application/json" \
  --data-raw '{"maxItems":1,"jobTitles":["attorney"],"locations":["Miami, Florida"]}'

Diese Gateway-API ist eine Vorschauversion; URL und Authentifizierung können sich ändern. Die Beispielparameter sind Musterdaten. Aufrufe werden mit $0.001/result einschließlich Servicegebühr abgerechnet.