Docs / Jobs

`publish_job_posting`

Publish a job posting draft, free or promoted.

This action can change or spend something, and when it does it happens right away. Read “Good to know” first.

What you give it

Input	What it is	Where to get it
`draftId` needed	A job id. The draft id (from create_job_posting, or list_job_postings category draft).	Run `list_job_postings` and use `jobPostings[].id` from its answer. 7 more places to get it `list_hiring_projects` → `projects[].jobPosting.id` `get_hiring_project` → `jobPosting.id` `get_job_posting` → `id` `create_job_posting` → `jobId` `edit_job_posting` → `jobId` `solve_job_posting_checkpoint` → `jobId` `publish_job_posting` → `jobId`
`mode` needed	One of: FREE, PROMOTED, PROMOTED_PLUS. FREE costs nothing. PROMOTED and PROMOTED_PLUS (ordinary postings only) are paid.	You write it.
`budget` optional	A group of fields. Paid modes only: the most to spend per day or per month. What goes inside `period` (needed): one of: daily, monthly. `currency` (needed): text, up to 3 characters. `amount` (needed): a number.	You write it.
`service` optional	One of: CLASSIC, RECRUITER. Which LinkedIn product the job posting belongs to (default CLASSIC).	You write it.
`hiringPhotoFrame` optional	True or false. Add the #Hiring frame to your profile picture.	You write it.
`bypassEmailVerification` optional	True or false. Skip LinkedIn's check that you may post for this company.	You write it.
`connectionId` optional	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 `get_my_profile` → `accounts[].connectionId` `list_connections` → `connections[].connectionId` `list_connections` → `summary.accounts[].connectionId` `list_sent_invitations` → `pendingInvitations[].connectionId` `preview_withdraw_invitations` → `breakdown[].linkedinConnectionId` `list_conversations` → `inbox[].linkedinConnectionId` `list_inmail` → `inmail[].connectionId` `get_inmail_credits` → `accounts[].connectionId` `list_sales_navigator_contracts` → `accounts[].connectionId` `who_is_waiting_on_me` → `waitingOnYou[].connectionId` `who_went_cold` → `coldConversations[].connectionId` `connections_never_messaged` → `summary.accounts[].connectionId` `get_usage` → `connectionId` `get_conversation` → `connectionId` `get_inmail_conversation` → `connectionId`

Call it

curl -X POST https://api.heyreagent.com/v1/actions/publish_job_posting \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{"draftId":"PASTE_JOB_ID_HERE","mode":"FREE"}'

The same call in JavaScript

const response = await fetch("https://api.heyreagent.com/v1/actions/publish_job_posting", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_KEY",
    "content-type": "application/json",
  },
  body: JSON.stringify({
    "draftId": "PASTE_JOB_ID_HERE",
    "mode": "FREE"
  }),
});
const answer = await response.json();
console.log(answer);

The same call in Python

import requests

response = requests.post(
    "https://api.heyreagent.com/v1/actions/publish_job_posting",
    headers={"Authorization": "Bearer YOUR_KEY"},
    json={
        "draftId": "PASTE_JOB_ID_HERE",
        "mode": "FREE",
    },
)
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/publish_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

{
  "draftId": "PASTE_JOB_ID_HERE",
  "mode": "FREE"
}

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:

`draftId`
`mode`
`paid`
`from`	the account it ran on
`usedToday`	number
`dailyLimit`	number
`jobState`	active \| draft \| review \| closed \| paused
`jobId`	A job id. Other actions take it.
`type`	EMAIL_VERIFICATION \| OTP

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

draftId is the job id of a draft: from create_job_posting, or list_job_postings with category "draft".
Two answers are possible. Published: jobState and jobId. Not yet: type EMAIL_VERIFICATION or OTP, and LinkedIn has sent a code — pass it to solve_job_posting_checkpoint.

In Claude or ChatGPT

Once connected, ask in your own words. The assistant sees this action as a tool with the same name, publish_job_posting, and the same inputs.