## jobs/linkedin/search

`GET /v1/jobs/linkedin/search`

Search LinkedIn job postings by keywords, location, organisation, date, employment type, experience level and workplace type.

*LinkedIn job search*

| Parameter | Required | Description |
| --- | --- | --- |
| `query` | no | Keywords, title, company or position — e.g. `data engineer` |
| `location` | no | Country or city; worldwide when empty — e.g. `London` |
| `organization_ids` | no | Organisation ids from jobs/linkedin/organizations, semicolon-separated — e.g. `1441` |
| `date_posted` | no | month, week or day — e.g. `week` |
| `employment_types` | no | contractor, fulltime, parttime, intern or temporary — e.g. `fulltime;parttime` |
| `experience_levels` | no | intern, entry, associate, midSenior or director — e.g. `midSenior` |
| `workplace_types` | no | remote, hybrid or onSite — e.g. `remote` |
| `cursor` | no | Cursor from the previous page |
| `dry_run` | no | Read a zero-credit estimate without fetching sources, running AI, or reserving credits. Cache status is a snapshot, not a guarantee at execution. — e.g. `1` |

**Cost:** 3 credits at list price per successful uncached response; variable-cost operations may quote or settle a different charge. Confirmed uncharged or refunded failures report zero. Pending reconciliation can report credits_used:null; retain request_id and the original idempotency key.

```bash
curl "https://www.monocrawl.com/v1/jobs/linkedin/search?query=data%20engineer" \
  -H "x-api-key: mn_your_key_here"
```

### Response data

Illustrative abbreviated data; documented core fields are optional and may be null. Additional source fields are allowed.

```json
{
  "items": [],
  "count": 0,
  "cursor": null
}
```

[Field reference](https://www.monocrawl.com/docs/endpoints/jobs/linkedin/search#response) · [JSON Schema for response.data](https://www.monocrawl.com/schemas/jobs/linkedin/search.json)