Docs / Recruiter

`reject_recruiter_applicant`

Reject one applicant in a hiring project, with a reason.

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
`applicantId` needed	A Recruiter id. The applicant's Recruiter id (AE…).	Run `search_linkedin_recruiter_people` and use `results[].id` from its answer.
`hiringProjectId` needed	A hiring project id. The hiring project (from list_hiring_projects).	Run `list_hiring_projects` and use `projects[].id` from its answer. 2 more places to get it `get_hiring_project` → `id` `create_job_posting` → `projectId`
`reason` needed	One of: NOT_MEET_BASIC_QUALIFICATIONS, NOT_IN_DESIRED_LOCATION, MORE_QUALIFIED_CANDIDATES, WITHDREW_APPLICATION, NOT_CONSIDERED_OR_REASON_NOT_SPECIFIED.	You write it.
`notifyMessage` optional	Text, up to 4000 characters. Text of the rejection notice to send the applicant. Omit to reject without telling them.	You write it.
`notifyAt` optional	A date and time, like 2026-10-01T00:00:00.000Z. When to send the notice (ISO 8601 UTC). Default: now.	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/reject_recruiter_applicant \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{"applicantId":"PASTE_RECRUITER_ID_HERE","hiringProjectId":"PASTE_HIRING_PROJECT_ID_HERE","reason":"NOT_MEET_BASIC_QUALIFICATIONS"}'

The same call in JavaScript

const response = await fetch("https://api.heyreagent.com/v1/actions/reject_recruiter_applicant", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_KEY",
    "content-type": "application/json",
  },
  body: JSON.stringify({
    "applicantId": "PASTE_RECRUITER_ID_HERE",
    "hiringProjectId": "PASTE_HIRING_PROJECT_ID_HERE",
    "reason": "NOT_MEET_BASIC_QUALIFICATIONS"
  }),
});
const answer = await response.json();
console.log(answer);

The same call in Python

import requests

response = requests.post(
    "https://api.heyreagent.com/v1/actions/reject_recruiter_applicant",
    headers={"Authorization": "Bearer YOUR_KEY"},
    json={
        "applicantId": "PASTE_RECRUITER_ID_HERE",
        "hiringProjectId": "PASTE_HIRING_PROJECT_ID_HERE",
        "reason": "NOT_MEET_BASIC_QUALIFICATIONS",
    },
)
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/reject_recruiter_applicant`
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

{
  "applicantId": "PASTE_RECRUITER_ID_HERE",
  "hiringProjectId": "PASTE_HIRING_PROJECT_ID_HERE",
  "reason": "NOT_MEET_BASIC_QUALIFICATIONS"
}

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:

`rejected`
`applicantId`
`hiringProjectId`
`reason`
`notified`
`from`	the account it ran on
`usedToday`	number
`dailyLimit`	number

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

applicantId is the person's Recruiter id, not the applicant id that list_job_applicants returns.

In Claude or ChatGPT

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