LinkedIn API
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.
Endpoint
GET/v1/linkedin/company-jobslive · proven3 creditsParameters
Query parameters
| Name | Required | Description | Example |
|---|---|---|---|
organization_id | yes | LinkedIn organisation id (from jobs/linkedin/organizations) | 1441 |
query | no | Keywords to narrow the roles | engineer |
location | no | Country or city | 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. | 1 |
Examples
Make the request
curl "https://www.monocrawl.com/v1/linkedin/company-jobs?organization_id=1441&query=engineer" \ -H "x-api-key: mn_your_key_here"
TypeScript
const key = process.env.MONOCRAWL_API_KEY;
if (!key) throw new Error('Set MONOCRAWL_API_KEY on your server.');
const res = await fetch(
"https://www.monocrawl.com/v1/linkedin/company-jobs?organization_id=1441&query=engineer",
{ headers: { "x-api-key": key } },
);
const body = await res.json();
if (!body.success) {
// one error shape for every endpoint — see /docs/errors
throw new Error(`${body.error.type}: ${body.error.message}`);
}
console.log(body.data, "credits left:", body.credits_remaining);Python
import os
import requests
res = requests.get(
"https://www.monocrawl.com/v1/linkedin/company-jobs?organization_id=1441&query=engineer",
headers={"x-api-key": os.environ["MONOCRAWL_API_KEY"]},
timeout=60,
)
body = res.json()
if not body["success"]:
# one error shape for every endpoint — see /docs/errors
raise RuntimeError(f"{body['error']['type']}: {body['error']['message']}")
print(body["data"], "credits left:", body["credits_remaining"])Response
Response fields and example
This example is illustrative, not a captured live response. Variable-cost operations may settle a charge different from the list price below. A successful response puts the platform payload in data and reports the exact credits used, remaining balance, request id and cache status beside it.
{
"success": true,
"platform": "linkedin",
"endpoint": "/v1/linkedin/company-jobs",
"data": {
"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
},
"credits_used": 3,
"credits_remaining": 99,
"request_id": "req_…",
"cached": false
}The example is illustrative and shows a documented subset of data. The fields below are optional across supported sources; nullable fields can also be absent. Preserve unknown values and accept additional fields.
Schema basis: observed response shapes, not an exhaustive field specification. See schema coverage and validation limits.
Download the data JSON Schema. Validate response.data, not the whole envelope. A valid shape does not establish that every field or source record was returned.
| Field inside data | Type | Meaning |
|---|---|---|
count | number | null | Number of records in this response, not lifetime or total matches. |
cursor | string | null | Opaque next-page token; pass it back unchanged. Null does not prove complete history. |
dropped | number | null | Optional dropped supplied by this operation. Null means unknown. |
has_more | boolean | null | Source continuation indicator; null means unknown. |
items | array | null | Returned records. Source coverage and completeness vary. |
items[].benefits | array | null | Source array was empty in the reviewed captures; item fields remain unspecified. |
items[].board | string | null | Optional board supplied by this operation. Null means unknown. |
items[].company | object | null | Optional company supplied by this operation. Null means unknown. |
items[].company.addresses | array | null | Source array was empty in the reviewed captures; item fields remain unspecified. |
items[].company.name | string | null | Optional name supplied by this operation. Null means unknown. |
items[].date_posted | string | null | Optional date posted supplied by this operation. Null means unknown. |
items[].id | string | null | Source identifier. Preserve the supplied type and exact value. |
items[].industries | array | null | Source array was empty in the reviewed captures; item fields remain unspecified. |
items[].location | string | null | Optional location supplied by this operation. Null means unknown. |
items[].platform | string | null | Optional platform supplied by this operation. Null means unknown. |
items[].posted | string | null | Optional posted supplied by this operation. Null means unknown. |
items[].skills | array | null | Source array was empty in the reviewed captures; item fields remain unspecified. |
items[].title | string | null | Source title when supplied. |
items[].url | string | null | Original source URL when supplied. |
total | number | null | Source-reported total; null is unknown. |
Optional fields reviewed from preserved successful responses. Additive fields and source variations remain allowed; validate the fields your workflow requires.
The example is invented and illustrates types only; zero and empty values are not claims about a real result.
Failures use the typed error envelope. A confirmed uncharged or refunded failure reports zero; a pending reconciliation can report an unknown charge. Read credits_used and error.details.billing_status, and keep request_id for recovery. Response contract · Error reference