Talent namespace

List or retrieve candidate talent records when the authenticated user has the required access.

Only candidate profiles whose visibility is public can be returned. Board configuration can disable the directory or restrict it to entitled employers.

board.talent.list()

1234567
list(query?: {
  cursor?: string;
  q?: string;
  skill?: string;
  limit?: number;
  offset?: number;
}, options?: FetchOptions): Promise<TalentDirectoryListEnvelope>

Lists public candidate cards, ranked by job-search status and recent profile activity.

12345
const { data, hasMore, nextCursor, count } = await board.talent.list({
  q: 'frontend',
  skill: 'react',
  limit: 20,
});

limit accepts 1–100. offset (candidates to skip) takes precedence over cursor. The envelope carries the total count alongside the page limit/offset; iterate forward with the opaque nextCursor or page in parallel with offset. offset + limit above 10,000 returns 400 (pagination_offset_too_large).

board.talent.retrieve()

1
retrieve(handle: string, options?: FetchOptions): Promise<TalentProfile>

Retrieves a public candidate by profile handle or board-user ID.

123
const profile = await board.talent.retrieve('jane-doe');

console.log(profile.headline, profile.experiences, profile.skills);

The profile contains its public header plus experience, education, skills, and languages. Job-search status can be null when the candidate exposes it only to employers.

Authorization and errors

• talent_directory_not_found (404)—the directory is disabled.
• talent_directory_restricted (403)—the current viewer needs employer access; render the employer sign-in or upgrade journey.
• talent_not_found (404)—the handle is unknown or the profile is not public. Do not reveal which case applies.

When access depends on a bearer or employer entitlement, bypass shared caches. A feature flag can hide the route early, but only the API response authorizes the viewer.