canonical: https://jentic.com/apis/apiproxy.shared.lumessetalentlink.com/talentlink

# Apiproxy Shared Lumessetalentlink Talentlink REST API Documentation

Jentic publishes the only available OpenAPI specification for the Cornerstone TalentLink REST API, keeping it validated and agent-ready. TalentLink is Cornerstone's enterprise applicant tracking system and the REST API exposes 178 endpoints across candidates, applications, requisitions, contracts, advertisements, selection processes, interviews, assessments, and timesheets. Authentication uses paired apiKey, username, password, and access-token headers issued by Cornerstone. The API powers integrations that move candidates and applications between TalentLink and external job boards, assessment vendors, HRIS, and onboarding tools.

## For AI agents

Manage candidates, applications, requisitions, advertisements, selection processes, and assessments across 178 Cornerstone TalentLink REST endpoints.

## Scope

Does not handle payroll, benefits administration, or learning management - use for applicant tracking and recruiting operations in Cornerstone TalentLink only.

## Capabilities

- List and update applications with their statuses through /application and `/application/status`
- Generate signed advertisement preview tokens and fetch advert details via `/advertisement/postings/{jobNumber}`
- Submit external assessment results, reports, and resources via `/assessment-provider/submit-`* endpoints
- Read and write candidate, contract, position, and department records through their respective resource paths
- Walk lookup-of-values catalogs (LOV) for configurable fields, free-form fields, and user data via /lov endpoints
- Drive selection processes, interview scheduling, and timesheet records for downstream HR systems

## Use cases

### Job board syndication

Pull published adverts from `/advertisement/postings/{jobNumber}` and post them to external job boards on a schedule, then push back applicant submissions to /application as they arrive. Because TalentLink owns the requisition and advert lifecycle, the integration only needs to mirror state, not duplicate it. The 178 endpoints cover the full advert and application surface required for two-way syndication.

Example prompt: GET `/advertisement/postings/{jobNumber}` for each open requisition, post to LinkedIn or Indeed, then POST /application when an applicant submits.

### Assessment provider integration

Plug an external assessment vendor into TalentLink's selection process by calling `/assessment-provider/submit-resource` to register the assessment URL, `/assessment-provider/submit-status` to update progress, and `/assessment-provider/submit-results` or `/assessment-provider/submit-report` to deliver outcomes. TalentLink advances the candidate through the configured selection step automatically once results land. This is the supported pattern for psychometric, coding, and case-study assessment vendors.

Example prompt: POST `/assessment-provider/submit-resource` with the assessment URL, then POST `/assessment-provider/submit-results` with the structured results form when complete.

### HRIS hand-off on hire

Once a candidate is marked hired in TalentLink, pull their contract record and supporting candidate fields and write them into the downstream HRIS so onboarding can begin. The /contract and /candidate endpoints expose stable identifiers and ISO-coded fields suitable for a clean ETL hand-off. This shortens the gap between offer-accepted and first-day systems access from days to minutes.

Example prompt: GET `/candidate/{candidateId}` and `/contract/{contractId}` on hire, then POST the resulting payload to your HRIS's employee-create endpoint.

### Agent-driven recruiting operations

An AI agent embedded in a recruiter's workflow can read application statuses, advance candidates through selection steps, and submit assessment results through Jentic without holding TalentLink credentials directly. The recruiter speaks in natural language, Jentic resolves the right TalentLink endpoints, and the agent executes them with credentials drawn from the vault. Audit trails remain inside TalentLink as if the recruiter performed the action directly.

Example prompt: Through Jentic, search 'update an application status', load the talentlink `/application/status` operation, and execute with the new status on the recruiter's behalf.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/application` | List applications |
| PUT | `/application/status` | Update an application status |
| GET | `/application/available-statuses` | Retrieve allowed application statuses |
| GET | `/advertisement/postings/{jobNumber}` | Fetch advert details for a requisition |
| POST | `/advertisement/generate-token` | Generate an advert preview token |
| POST | `/assessment-provider/submit-results` | Submit structured assessment results |
| POST | `/assessment-provider/submit-status` | Update assessment status for a candidate |

## Key resources

- **Candidate API** — Read and update candidate profiles.
- **Application API** — List, create, and update applications and their statuses.
- **Published Advert API** — Fetch and preview adverts attached to requisitions.
- **Selection Process API** — Drive candidates through the configured selection steps.
- **Assessment Provider API** — Submit assessment URLs, statuses, results, and reports.
- **Contract API** — Read contract records on hire for HRIS hand-off.
- **LOV API** — Walk configurable, free-form-field, and user-data lookup catalogs.

## Why Jentic

- **Setup:** Wiring the TalentLink REST API by hand means setting up its API key, learning the application and advertisement resource shapes, and threading status and assessment calls yourself. Through Jentic you install once, import TalentLink from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** TalentLink puts the job number in the URL path for advertisement postings while status changes and assessment results travel in the request, so scope the agent to the operations it needs, such as reading applications and available statuses, and leave out updating an application's status unless you add it. You choose the allowed operations, so the agent only calls what you list.
- **Credential handling:** Your TalentLink key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list job applications' or 'read available application statuses', and Jentic returns the matching TalentLink operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse Harvest API** — Modern REST API for the Greenhouse ATS.
- **Lever API** — REST API for the Lever ATS.
- **Workable API** — REST API for the Workable ATS.
- **Workday API** — Enterprise HRIS often paired with TalentLink for post-hire processes.

## FAQ

### Why is there no official OpenAPI spec for Talentlink REST API Documentation?

Cornerstone TalentLink does not publish a downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Talentlink REST API Documentation via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer .

### What authentication does the TalentLink REST API use?

The API uses paired apiKey, username, password, and access-token headers issued by Cornerstone. All four are declared as apiKey-style schemes in the spec and must be supplied per request. Through Jentic the credentials are stored in the vault and applied to each call server-side.

### How do I update an application's status through Jentic?

Search Jentic for 'update an application status', load the talentlink `/application/status` operation, and execute with the applicationId and the target status. Run `/application/available-statuses` first to confirm the status is valid for that application's current step.

### Can I push external assessment results back into TalentLink?

Yes. Use POST `/assessment-provider/submit-results` for structured form-based results, `/assessment-provider/submit-report` to attach a physical report file, `/assessment-provider/submit-resource` to register an assessment URL, and `/assessment-provider/submit-status` to update progress.

### How do I fetch advert details for a requisition?

Call GET `/advertisement/postings/{jobNumber}` with the requisition's job number to retrieve all adverts attached to it. For unpublished adverts that need a preview, POST `/advertisement/generate-token` first to obtain a signed URL.

### What are the rate limits for the TalentLink REST API?

Rate limits are not declared in the OpenAPI spec. TalentLink applies tenant-specific limits configured by Cornerstone; coordinate with your account team and watch for HTTP 429 responses to back off appropriately.

### Can I limit what my agent is allowed to do with the Cornerstone TalentLink REST API?

Yes. Jentic One is self-hosted, so you set the rules and pick exactly which TalentLink operations the agent may call and which credentials it may use. For example, you can allow read-only access to GET /application and GET `/application/available-statuses` while leaving PUT `/application/status` off the list, so the agent can review applications but not change their status unless you add that operation. You can do the same for advertisement lookups and the /assessment-provider submit operations, granting only the calls the agent actually needs.