A company first LinkedIn job search API.
Broad job search APIs begin with a title and location, then return roles from whichever employers match. Curly reverses that model. The company list is required, while titles, locations, posting age, result limits, and full detail enrichment remain optional.
This makes the API suitable for repeatable target account monitoring. A workflow can scan the same companies every day, keep the LinkedIn job ID as a stable key, and route only newly observed roles into research, sales, recruiting, or analytics systems.
Fast listing discovery or full job details.
Use includeDetails: false when the signal only needs a role, company, location, publication date, and source URL. This avoids visiting every job page and is the preferred mode for frequent monitoring.
Enable detail enrichment when a downstream workflow needs the public description, employment criteria, salary, applicant count, workplace type, expiration, or application metadata. Missing public values remain empty instead of being guessed.
Know which fields each API mode returns.
| Fields | Fast mode | Full details | Purpose |
|---|---|---|---|
job_id, job_url | Included | Included | Stable source identity and verification |
title, company_name, location | Included | Included | Core company hiring signal |
published_at, scraped_at | Included | Included | Posting and collection timestamps |
description, employment_type | Not requested | When public | Role context and employment criteria |
salary, applicants, workplace_type | Not requested | When public | Qualification and prioritization |
application, benefits, expires_at | Not requested | When public | Application and listing lifecycle data |
search_keyword, search_location | Included | Included | Trace the filter that found each record |
details_status | not_requested | complete or unavailable | Distinguish missing data from skipped enrichment |
LinkedIn job posting API versus job search data.
LinkedIn talent integrations are designed for approved partners that publish and manage jobs for customers. They should not be confused with an open public API for searching LinkedIn job listings. Curly is an independent public data workflow and is not affiliated with or endorsed by LinkedIn.
| Option | Access | Best for | Search data |
|---|---|---|---|
| Official LinkedIn talent APIs | Approved partner access | Publishing and managing jobs for customers | Not a general public job search API |
| Curly free scraper | No account required | One company and up to 10 lightweight records | Browser based JSON and CSV export |
| Curly API on Apify | Apify API token | Company monitoring, bulk data and automation | Up to 100 companies with optional enrichment |
| Broad job database API | Provider account | Market wide job discovery by keyword | Company lists usually require downstream filtering |
Turn job data into company hiring signals.
Scheduled company scans can reveal investment in a function, movement into a new location, or repeated demand for a skill. The signal becomes more useful when the workflow preserves the company, title, location, dates, source URL, and filters that found each record.
- Build the tested Clay and Apify hiring signals workflow
Map target company inputs, route successful results, and deduplicate jobs before enrichment.
- Inspect a free single company result first
Validate the company and lightweight field structure before creating a recurring API integration.