One LinkedIn job posting by URL or id: title, full description, location, salary when disclosed, applicants, employment and workplace type, apply links, posting and expiry dates and the hiring company.
1 credit/ call
Never more than 7 credits a call.
You only pay when data comes back.
curl -X POST "https://api.primaryapi.com/v1/run/linkedin.job" \
-H "Authorization: Bearer $PRIMARYAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://www.linkedin.com/jobs/view/4011051212"}'{
"output": {
"found": true,
"data": {
"title": "<string | null>",
"applicants": "<integer | null>",
"views": "<integer | null>",
"remote": "<boolean | null>", …
}
},
"credits": 1
}Input and output
1 field
https://www.linkedin.com/jobs/view/4011….28 fields
Good to know
Closed postings that LinkedIn still shows come back with jobState "CLOSED".
Salary, views, benefits and the hiring team are only present when the posting shows them.
A job that no longer exists is a miss and is not charged.
Unknown URL? It comes back as not found, not as an error.
Terms of use. Public LinkedIn data only. LinkedIn’s User Agreement restricts automated collection and LinkedIn enforces it; use the data for lawful purposes, keep copies only as long as you need them, and treat post and article text as the author’s content (analysis, not republication). Results contain personal data about identifiable people (GDPR, UK GDPR, CCPA): have a lawful basis, honour deletion requests, and never use it for spam or unsolicited bulk outreach.
The same key and credits work for every API.