Docs / Jobs
get_job_posting
Read one of your job postings.
This action only reads. It changes nothing, so it is safe to try.
What you give it
| Input | What it is | Where to get it |
|---|---|---|
jobIdneeded | A job id. The job posting id (from list_job_postings). | Run list_job_postings and use jobPostings[].id from its answer.7 more places to get it
|
serviceoptional | One of: CLASSIC, RECRUITER. Which LinkedIn product the job posting belongs to (default CLASSIC). | You write it. |
connectionIdoptional | A connection id. Which of your LinkedIn accounts to act from (its id from list_linkedin_accounts). Omit to use your first live one. | Run list_linkedin_accounts and use accounts[].id from its answer.15 more places to get it
|
Call it
curl -X POST https://api.heyreagent.com/v1/actions/get_job_posting \
-H "Authorization: Bearer YOUR_KEY" \
-H "content-type: application/json" \
-d '{"jobId":"PASTE_JOB_ID_HERE"}'The same call in JavaScript
const response = await fetch("https://api.heyreagent.com/v1/actions/get_job_posting", {
method: "POST",
headers: {
"Authorization": "Bearer YOUR_KEY",
"content-type": "application/json",
},
body: JSON.stringify({
"jobId": "PASTE_JOB_ID_HERE"
}),
});
const answer = await response.json();
console.log(answer);The same call in Python
import requests
response = requests.post(
"https://api.heyreagent.com/v1/actions/get_job_posting",
headers={"Authorization": "Bearer YOUR_KEY"},
json={
"jobId": "PASTE_JOB_ID_HERE",
},
)
print(response.json())The same call in n8n
Add an HTTP Request node and fill it in like this:
| Method | POST |
| URL | https://api.heyreagent.com/v1/actions/get_job_posting |
| Send Headers | On. Name Authorization, Value Bearer YOUR_KEY |
| Send Body | On. Body Content Type JSON, Specify Body Using JSON, then paste the body below |
{
"jobId": "PASTE_JOB_ID_HERE"
}Put your own key where it says YOUR_KEY. Put your own value where it says PASTE_…_HERE: the table above says where each one comes from. New here? Start with your first call.
What you get back
When it worked, the answer is { "ok": true, "result": { … } }. Inside result:
id | A job id. Other actions take it. |
state | active | draft | review | closed | paused |
title | string |
description | string |
company | string |
companyId | string |
location | string |
applicantsCounter | number |
viewsCounter | number |
cost | number |
createdAt | number |
publishedAt | number |
closedAt | number |
applyUrl | string |
screeningQuestions[].question | string |
screeningQuestions[].favorableAnswers | string[] |
hiringTeam[].name | string |
hiringTeam[].providerId | string or null |
hiringTeam[].publicIdentifier | string or null |
hiringTeam[].profileUrl | string |
hiringTeam[].canSendFreeInmail | boolean |
salary | string |
workplace | string |
seniority | string |
skills | string[] |
functions | string[] |
industries | string[] |
A field that does not apply to an answer is left out, or is null.
When it did not work, the answer is { "ok": false, "error": "…", "message": "…" }. What each error means.
Good to know
- service must match where the posting lives: CLASSIC or RECRUITER.
In Claude or ChatGPT
Once connected, ask in your own words. The assistant sees this action as a tool with the same name, get_job_posting, and the same inputs.