canonical: https://jentic.com/apis/pcrecruiter.net/pcrecruiter

# PCRecruiter API

PCRecruiter API provides applicant tracking and recruitment CRM capabilities for staffing agencies and corporate hiring teams. It supports candidate, company, and position management with full CRUD operations, activity logging, attachment handling, education and work history tracking, pipeline interview and placement management, calendar events, and notification retrieval. The API serves permanent placement, third-party recruitment, and staffing/contracting workflows.

## For AI agents

Manage candidates, companies, positions, pipeline activities, interviews, placements, and calendar events for recruitment and staffing operations.

## Scope

Does not handle job board posting, background checks, or payroll - use for candidate tracking, pipeline management, and recruitment CRM operations only.

## Capabilities

- Create and manage candidate records with education, work history, and attachments
- Track companies with activity logs and relationship management
- Post and manage job positions with full lifecycle tracking
- Record pipeline activities, interviews, and placements across hiring workflows
- Manage calendar events for interview scheduling and follow-ups
- Attach resumes, cover letters, and documents to candidate profiles
- Retrieve notifications for workflow triggers and status updates

## Use cases

### Candidate Pipeline Management

Track candidates through the full recruitment pipeline from initial contact to placement. PCRecruiter manages pipeline steps, activities, interviews, and placements for each candidate-position combination. Recruiters create candidates via POST /candidatesV2, advance them through pipeline steps via POST /pipelineactivities, and record placements via POST /PipelinePlacements. The API provides step counts via GET `/pipelinesteps/counts/{stepId}` for pipeline analytics.

Example prompt: Create a new candidate via POST /candidatesV2 with name, email, and phone, then log a pipeline activity for position ID 'POS-001' advancing the candidate to the 'Phone Screen' step

### Position and Job Management

Create and manage open positions with full lifecycle tracking from requirement definition through hire. The API supports position CRUD (POST/GET/PUT/DELETE on /positionsV2), activity logging for each position, and linking candidates through the pipeline. This enables job board integrations, internal requisition tracking, and hiring progress reporting.

Example prompt: Create a new position via POST /positionsV2 with title 'Senior Developer', company ID, and location, then retrieve it by ID to confirm creation

### Recruitment Activity Logging

Record every recruiter interaction against candidates, companies, and positions. Activities include calls, emails, notes, meetings, and status changes. The API accepts activity entries via POST on the respective resource's activities endpoint and returns chronological activity feeds for relationship history and compliance audit trails.

Example prompt: Log a phone screen activity against candidate ID '12345' via POST `/candidatesV2/{id}/activities` with type 'Phone Call', notes, and date

### AI Agent Recruiting Automation via Jentic

AI agents use the PCRecruiter API through Jentic to search candidates, create pipeline activities, and schedule interviews without managing OAuth tokens directly. Agents search by intent, receive typed schemas for recruitment operations, and execute calls with Jentic handling Bearer token management. This enables automated candidate sourcing, pipeline advancement, and interview coordination.

Example prompt: Search Jentic for 'find candidates in PCRecruiter', load the schema for GET /candidatesV2, and execute with search parameters to find candidates matching 'python developer' in location 'Remote'

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/candidatesV2` | Search and list candidates |
| POST | `/candidatesV2` | Create a new candidate record |
| GET | `/positionsV2` | List open positions |
| POST | `/positionsV2` | Create a new position |
| POST | `/pipelineactivities` | Log a pipeline activity |
| POST | `/PipelineInterviews` | Record an interview event |
| POST | `/PipelinePlacements` | Record a placement |
| GET | `/pipelinesteps/counts/{stepId}` | Get candidate count at a pipeline step |

## Key resources

- **Candidates** — Full CRUD for candidate profiles with education, work history, and attachments
- **Companies** — Manage client and prospect company records with activities
- **Positions** — Create and manage open job positions with lifecycle tracking
- **Pipeline Activities** — Log recruiter activities and status changes in the hiring pipeline
- **Pipeline Interviews** — Record and manage interview events for candidates
- **Pipeline Placements** — Track successful candidate placements
- **Calendar** — Manage scheduling events for interviews and follow-ups
- **Notifications** — Retrieve workflow notifications and alerts

## Why Jentic

- **Setup:** Wiring the PCRecruiter API by hand means acquiring a bearer token via POST /access-token, refreshing it as it expires, and mapping its candidate, position, and pipeline resources yourself. Through Jentic you install once, import PCRecruiter from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** PCRecruiter carries most of its candidate and pipeline details in the request body and query, so scope the agent by the operations it needs, such as reading candidates or positions and pipeline step counts. You choose that set, so writes like creating candidates, positions, or pipeline placements are not included unless you add them.
- **Credential handling:** Your PCRecruiter credentials are stored once, encrypted, by your own Jentic One instance, which acquires and refreshes the bearer token and injects it at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find candidates matching skills' or 'log a pipeline activity', and Jentic returns the matching PCRecruiter operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Recruitee API** — Modern ATS with collaborative hiring features but less staffing agency focus
- **ZipRecruiter API** — Job distribution platform that feeds candidates into ATS pipelines
- **RecruiterFlow API** — Recruitment CRM designed for staffing agencies with automation features

## FAQ

### What authentication does the PCRecruiter API use?

The PCRecruiter API uses Bearer token authentication. You obtain an access token via POST /access-token with your credentials, then include it in the Authorization header for subsequent calls. Tokens can be refreshed or revoked via the same endpoint. Through Jentic, token lifecycle is managed automatically.

### Can I upload resumes to candidate records?

Yes. POST `/candidatesV2/{id}/attachments` accepts file uploads for resumes, cover letters, and other documents. Each attachment is linked to the candidate record and can be retrieved via GET `/candidatesV2/{id}/attachments` for viewing or download.

### What are the rate limits for the PCRecruiter API?

PCRecruiter applies per-token rate limits based on your subscription tier. Standard integrations support 120 requests per minute across all endpoints. Bulk operations on candidates and positions count individually against this limit.

### How do I search for candidates through Jentic?

Search Jentic for 'find candidates in PCRecruiter', load the schema for GET /candidatesV2, and execute with query parameters for skills, location, or availability. Jentic handles Bearer token injection and returns matching candidate records with their profile data.

### Does PCRecruiter track the full hiring pipeline?

Yes. The API provides pipeline steps (GET /pipelinesteps), pipeline activities (POST /pipelineactivities), interviews (POST /PipelineInterviews), and placements (POST /PipelinePlacements). Each tracks candidate progression from sourcing through placement with timestamps and recruiter notes.

### Can I manage company relationships with the PCRecruiter API?

Yes. The /companiesV2 endpoints support full CRUD for company records. You can create companies, log activities against them via POST `/companiesV2/{id}/activities`, and link positions to companies for client relationship tracking.

### Can I limit what my agent is allowed to do with the PCRecruiter API?

Yes. Because you run Jentic One yourself, your own rules decide which PCRecruiter operations and credentials the agent may use, so you can grant read-only access such as listing candidates via GET /candidatesV2, listing positions via GET /positionsV2, and checking pipeline step counts via GET `/pipelinesteps/counts/{stepId}.` Write operations like creating candidates with POST /candidatesV2, creating positions with POST /positionsV2, or recording placements with POST /PipelinePlacements are not included unless you add them to that set. The agent can only call the operations you have explicitly allowed.