get_candidate

Input

Parameter	Type	Required	Description
`candidateId`	string	Yes	Candidate id to fetch.

Output

JSON block with success: true and nested candidate plus secured talent. Contact objects are not returned directly: visible emails are exposed as talent.emails, and visible sanitized phone numbers are exposed as talent.phones. The response also includes contactsLoading for email and phone while enrichment jobs run. The candidate object exposes sourcingId for the sourcing that owns the candidate. The talent object does not include internal LinkedIn/email/WhatsApp interaction flags. The response does not expose internal workspaceId or userId fields.

Outreach activity

data also carries lastActivityAt, lastActivityDirection, lastActivityChannel, lastActivityContent and replyStatus: the latest outreach activity between the talent and the user who owns the API key, aggregated across every channel (LinkedIn, email, WhatsApp, SMS) and across legacy and dynamic sequences. Messages and invitations sent by other members of the workspace are not taken into account. They are computed with the same rules as get_candidates, so a candidate returns identical values from both tools.

Field	Type	Description
`lastActivityAt`	ISO-8601 string \| `null`	Date of the most recent outreach event: message sent, LinkedIn invitation sent or accepted, or reply received. `null` when the candidate was never contacted.
`lastActivityDirection`	`INBOUND` \| `OUTBOUND` \| `null`	`INBOUND` when the latest event comes from the talent (reply, accepted invitation), `OUTBOUND` when it comes from the API key owner (message or invitation sent). `null` when the candidate was never contacted.
`lastActivityChannel`	`LINKEDIN` \| `WHATSAPP` \| `EMAIL` \| `SMS` \| `null`	Channel of that latest event. `null` when the candidate was never contacted.
`lastActivityContent`	string \| `null`	Text of that latest event when it is a sent or received message. `null` when the candidate was never contacted, when the latest event is a LinkedIn invitation sent or accepted (Kalent does not store the invitation note), or when the message body is empty. Email subject is not included.
`replyStatus`	`REPLIED` \| `NO_REPLY` \| `NOT_CONTACTED`	`REPLIED` as soon as at least one reply was received on any channel, `NO_REPLY` when the talent was contacted without any reply, `NOT_CONTACTED` when no outreach happened.

replyStatus stays REPLIED even if a follow-up was sent after the talent replied (lastActivityDirection then becomes OUTBOUND). An accepted LinkedIn invitation counts as an inbound activity but not as a reply.

{
  "success": true,
  "data": {
    "candidate": {
      "id": "candidate_123",
      "statusHandle": "CONTACTED",
      "createdAt": "2026-05-19T09:00:00.000Z",
      "sourcingId": "sourcing_123",
      "talentId": "talent_123"
    },
    "talent": {
      "id": "talent_123",
      "firstname": "Grace",
      "lastname": "Hopper",
      "emails": ["grace@example.com"],
      "phones": [],
      "contactsLoading": { "email": false, "phone": false }
    },
    "lastActivityAt": "2026-05-21T14:32:00.000Z",
    "lastActivityDirection": "INBOUND",
    "lastActivityChannel": "LINKEDIN",
    "lastActivityContent": "Yes, I am interested.",
    "replyStatus": "REPLIED"
  }
}

Errors

session not found or Not found when the candidate is outside the session workspace.

Getting Started

Tools

Input

Output

Outreach activity

Errors

​Input

​Output

​Outreach activity

​Errors

Input

Output

Outreach activity

Errors