## linkedin/company-jobs

`GET /v1/linkedin/company-jobs`

Open roles at a company, one page at a time: title, location, posting time, employment type, seniority, remote flag, salary where stated and applicant count.

*LinkedIn company jobs*

| Parameter | Required | Description |
| --- | --- | --- |
| `organization_id` | yes | LinkedIn organisation id (from jobs/linkedin/organizations) — e.g. `1441` |
| `query` | no | Keywords to narrow the roles — e.g. `engineer` |
| `location` | no | Country or city — e.g. `London` |
| `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/linkedin/company-jobs?organization_id=1441&query=engineer" \
  -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
{
  "count": 0,
  "cursor": null,
  "dropped": 0,
  "has_more": false,
  "items": [
    {
      "benefits": [],
      "board": "example",
      "company": {
        "addresses": [],
        "name": "example"
      },
      "date_posted": "2026-09-01T12:00:00Z",
      "id": "example",
      "industries": [],
      "location": "example",
      "platform": "example",
      "posted": "example",
      "skills": [],
      "title": "example",
      "url": "https://example.com/example"
    }
  ],
  "total": 0
}
```

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