rc.openPersonPage

Open a candidate's profile in LinkedIn Recruiter Lite and, optionally, read their details and the recruiting activity your seat has with them. Use it on its own with a Recruiter profile URL, or under rc.doForPeople for each candidate of a search.

The account needs a Recruiter Lite seat and Linked API's Plus plan – see Recruiter Lite.

Constraints

⏺️ Root Start: allowed, when personUrl parameter is provided.

⬆️ Parent Actions: rc.doForPeople.

⬇️ Child Actions: N/A.

Parameters

{
  "actionType": "rc.openPersonPage",
  "label": "candidate1",
  "personUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId1",
  "basicInfo": true,
  "recruitingActivity": true
}

In AI assistants, the MCP tool is rc_fetch_person. The n8n action is Fetch person in Recruiter Lite; the Make module is Fetch Person in Recruiter Lite.

ParameterDescription
labelOptional. Label included in workflow completion.
personUrlRequired at the root, not allowed under rc.doForPeople, which supplies it. A Recruiter profile URL, https://www.linkedin.com/talent/profile/…, such as recruiterProfileUrl from rc.searchPeople or rc.retrieveProjectCandidates, or the personRecruiterUrl of a Recruiter Lite inbox message. A public profile URL (linkedin.com/in/…) is rejected with invalidWorkflow.
basicInfoOptional. true to read the candidate's details. Defaults to false. The SDK method rcFetchPerson, the CLI, the MCP tool, n8n and Make default it to true.
recruitingActivityOptional. true to read how much recruiting activity your seat has with the candidate. Defaults to false.

Each call counts as one Recruiter profile view in the rcPersonProfileViews limit, whichever fields you ask for.

When the Recruiter profile links to the candidate's public LinkedIn profile, Linked API remembers that link, whichever fields you ask for. Inbox polling by the candidate's public URL can then find their Recruiter conversation.

Result options

  1. Successful opening:
json
{
  "actionType": "rc.openPersonPage",
  "label": "candidate1",
  "success": true,
  "data": {
    "name": "Jane Example",
    "recruiterProfileUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId1",
    "headline": "Senior Backend Engineer at Example Cloud",
    "location": "Berlin, Germany",
    "avatarUrl": "https://media.licdn.com/dms/image/v2/C4D03AQExample/profile-displayphoto-shrink_100_100/0/1600000000000",
    "viewerState": { "connectionDegree": "2nd" },
    "publicUrl": "https://www.linkedin.com/in/jane-example",
    "industry": "Software Development",
    "recruitingActivity": {
      "projects": 2,
      "messages": 0,
      "feedback": 0,
      "attachments": 1
    }
  }
}

With basicInfo:

FieldMeaning
nameCandidate's full name.
recruiterProfileUrlThe Recruiter profile that was opened, without query parameters.
headlineHeadline, or an empty string.
locationLocation, or an empty string.
avatarUrlProfile photo URL, or null without a photo.
viewerState.connectionDegree1st, 2nd or 3rd+, as Recruiter shows it next to the name, or null when it shows none or when the interface language is not supported.
publicUrlThe candidate's public LinkedIn profile, https://www.linkedin.com/in/…. Pass it to the standard actions, such as st.openPersonPage.
industryIndustry of the candidate's current employer, as the profile shows it, or null.

With recruitingActivity, the counts Recruiter shows on the profile's recruiting activity tabs, for your seat:

FieldMeaning
recruitingActivity.projectsThe count on the Projects tab: your projects the candidate is in.
recruitingActivity.messagesThe count on the Messages tab.
recruitingActivity.feedbackThe count on the Feedback tab.
recruitingActivity.attachmentsThe count on the Attachments tab.

Each group of fields is present only when you ask for it. With basicInfo and recruitingActivity both false, the action only opens the profile, and data is an empty object.

label is included only if specified in the action parameters.

  1. Failed opening:
json
{
  "actionType": "rc.openPersonPage",
  "label": "candidate1",
  "success": false,
  "error": {
    "type": "personNotFound",
    "message": "This Recruiter profile could not be opened."
  }
}

Possible error.type values:

  • personNotFound – Recruiter kept the profile URL but did not show the profile.
  • recruiterSignInRequired, recruiterTwoStepVerificationRequired, recruiterMultipleSessionsDetected – the seat needs attention, see account errors.
  • limitExceeded – the account reached its rcPersonProfileViews limit.
  • unexpectedError – the profile could not be read: for example, Recruiter opened another page instead of the profile, or basicInfo was requested and the profile shows no public profile link.

Under rc.doForPeople, a failure stops the search at that candidate – see Results and paging.