Taleez MCP by usefulapi

WRITE: associate existing candidates to a job so they appear in its recruitment pipeline (the vendor's 'add candidates to a job'; this is an association made by the recruiter, not a candidate application, and this call sends no message). Pass location_id for a job with several locations. POST /0/jobs/{id}/candidates.

WRITE: add existing candidates to a talent pool (see taleez_list_pools). Adding a candidate already in the pool is harmless. No message is sent. POST /0/pools/{id}/candidates.

WRITE: add a new candidate to the Taleez database (first and last name required; the e-mail, if given, must be unique in the company). Creates a record only: the candidate is not attached to a job and no e-mail is sent by this call. Not idempotent: calling twice with no mail creates two candidates. POST /0/candidates.

One candidate by id: name, mail, phone, language, location, social links, unit, CV link and custom properties. GET /0/candidates/{id}.

Where a candidate stands: every application or association (type SPONTANEOUS, APPLICATION_TO_A_JOB, ASSOCIATED_TO_A_JOB...) with the job id, current pipeline step, rejected/hired dates and the step history. GET /0/candidates/{id}/applications.

The documents attached to a candidate (CV, cover letter...): id, name, date, size and file URL. GET /0/candidates/{id}/documents.

The events (interviews, calls, meetings) scheduled with a candidate: subject, start/end, location, meeting URL, attendees. GET /0/candidates/{id}/events.

The talent pools a candidate belongs to (pool id, name, date added, referrer). GET /0/candidates/{id}/pools.

The custom property values of a candidate (property id, name key, type, value or choices). GET /0/candidates/{id}/properties.

One job posting by id with its full details: descriptions, contract, location, recruiter, unit, tags, custom properties, public and application URLs. GET /0/jobs/{id}.

The total number of jobs and the job counts per status, contract, city, tag and company label (only values with at least one job). A quick overview of the hiring activity. GET /0/jobs/filters.

The questions candidates answer when applying to a job (id, label, type, required, choices). GET /0/jobs/{id}/questions.

The status history of a job: each change (date timestamp, status DRAFT/PUBLISHED/SUSPENDED/DONE). GET /0/jobs/{id}/statuses.

The recruitment pipeline steps of a job in order (id, name, order). Use them to read where each candidate stands. GET /0/jobs/{id}/steps.

The custom candidate properties defined in the account (id, name, type, choices, disabled). Use the ids with taleez_set_candidate_properties. GET /0/candidate-properties.

List the candidates in the company (id, name, mail, phone, language, location, social links, unit, creation date). Filter by exact e-mail address to find one person. Custom properties only with with_props. Candidates contain personal data: use it only for the user's own recruiting. GET /0/candidates.

List the company's calendar events (interviews, meetings): subject, start/end timestamps, location, meeting URL, job id, attendees. GET /0/events.

The custom job properties defined in the account (id, name, type, choices). GET /0/job-properties.

List the job postings of the company (id, label, status DRAFT/PUBLISHED/DONE/SUSPENDED, contract, location, recruiter, unit, tags, visibility, public URL). Filter by status, contract, unit, city, tag, company label or visibility; sort by creation or publication date. Job and profile descriptions are only included with with_details. GET /0/jobs.

The candidates in one talent pool. Custom properties only with with_props. GET /0/pools/{id}/candidates.

List the talent pools of the company (id, name, dates, recruiter). GET /0/pools.

List the recruiters (users) of the company. Use the ids to read who owns a job or to credit a new candidate. GET /0/recruiters.

List the units (entities, subsidiaries, sites) of the company. Use the ids to filter jobs. GET /0/units.

WRITE: set custom property values on a candidate. For a property without choices pass value (DATE as yyyy-MM-dd); for a property with choices pass choices (choice ids, see taleez_list_candidate_properties). An empty choices list removes all selected choices unless append_choices is true. Overwrites the previous values of the listed properties. POST /0/candidates/{id}/properties.

WRITE: change a candidate's name, e-mail, phone, social links or location. The current record is read first and unchanged name, mail and phone are sent back, so only what you pass changes (Taleez' update endpoint otherwise needs first and last name). Social links and location, when given, REPLACE the existing ones (an empty social_links object removes them all). Overwrites data; no message is sent. POST /0/candidates/{id}.