[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Vincere API and MCP server

> Vincere has an API, but only partners can get a key (checked 22 Oct 2026). Vincere issues API keys only to partners with a formal agreement, and it has no official MCP server. The Zapier app is the one open connection: 9 triggers and 6 actions, mostly new-record events and VinnyChat messages.

Recruitment CRM and applicant tracking system for staffing agencies: candidates, jobs, a pipeline from Applications to Placed, client LiveLists, tasks and activity logs in one tenant.

## What is the Vincere API?

Cotlet's Vincere API exposes 13 endpoints for your own Vincere account: list jobs, get job, list candidates, get candidate, list job applications, list tasks, list activities, add comment, add task, shortlist candidates, send candidates to a client, send job list to candidates and move application stage. The list_jobs endpoint returns jobs of your agency with company, contact, owner, status and sourcing dates. Each endpoint takes simple JSON inputs like job_id, limit or cursor and works both as an operation of the vincere_read or vincere_write MCP tool for agents and as a REST call for scripts.

- **Category:** [HR & recruiting](https://cotlet.dev/integrations/category/hr-recruiting.md)
- **Endpoints:** 13 (7 read, 6 write)
- **Updated:** 2026-10-18

Vincere has an API, but only partners can get a key (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Vincere with 13 endpoints (7 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Vincere have an official API?

Vincere has an API, but only partners can get a key (checked 22 Oct 2026). Vincere issues API keys only to partners with a formal agreement, and it has no official MCP server. The Zapier app is the one open connection: 9 triggers and 6 actions, mostly new-record events and VinnyChat messages.

| Task | Vincere official | Cotlet |
|---|---|---|
| Read jobs and candidates | Partly: Zapier only fires when a candidate, job or placement is created | Yes |
| Shortlist candidates to a job | No: No Zapier action; the API needs a partner agreement | Yes |
| Send candidates to a client as a LiveList | No: No Zapier action; the API needs a partner agreement | Yes |
| Send a job list to candidates | No: No Zapier action; the API needs a partner agreement | Yes |
| Move a candidate to the next pipeline stage | No: No Zapier action; the API needs a partner agreement | Yes |
| Log a comment on a candidate | No: No Zapier action; the API needs a partner agreement | Yes |
| Create a task | No: No Zapier action; the API needs a partner agreement | Yes |
| Read tasks and the activity log | No: No Zapier trigger for them | Yes |

Sources: [Vincere Help: Understanding and requesting API keys](https://help.vincere.io/en/articles/9618701-understanding-and-requesting-api-keys), [Vincere Help: Set up and use the Zapier integration](https://help.vincere.io/en/articles/3394931-set-up-and-use-the-zapier-integration), [Vincere on Zapier: triggers and actions](https://zapier.com/apps/vincere/integrations), [Vincere Help: Candidate Actions](https://help.vincere.io/en/articles/11143948-candidate-actions)

## For AI agents

```text
Vincere has an API, but only partners can get a key (checked 22 Oct 2026). Vincere issues API keys only to partners with a formal agreement, and it has no official MCP server. The Zapier app is the one open connection: 9 triggers and 6 actions, mostly new-record events and VinnyChat messages.
Cotlet provides a hosted MCP server and REST API for Vincere: 13 tools (7 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=vincere, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    vincere_read, vincere_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/vincere, each operation at its own route, e.g. POST /api/v1/vincere/jobs/{job_id}/candidates/shortlist
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_jobs, get_job, list_candidates, get_candidate, list_job_applications, list_tasks, list_activities, add_comment, add_task, shortlist_candidates, send_candidates_to_client, send_job_list_to_candidates, move_application_stage
Confirm      add_comment, add_task, shortlist_candidates, send_candidates_to_client, send_job_list_to_candidates, move_application_stage (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/vincere-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=vincere, requests Vincere in the Cotlet console and creates an API key there.
2. The user signs in to Vincere once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Vincere for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Vincere server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Vincere in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Vincere only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Vincere login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Vincere's terms; Cotlet is not affiliated with Vincere.
```

## What can an AI agent do in Vincere?

Cotlet is best for recruiting agency teams on Vincere who want an AI agent to shortlist candidates, send LiveLists and log calls without running or fixing a server.

- **[Shortlist candidates for a job](https://cotlet.dev/integrations/vincere-api-mcp-server/shortlist-candidates-for-a-job.md)** (runs: daily): "For the open job "Senior Java Developer" in Vincere, find candidates in the Java talent pool, skip anyone already on that job, and shortlist the ones whose current title is a developer role. List the rest for me." → `list_jobs`, `get_job`, `list_candidates`, `get_candidate`, `shortlist_candidates`, `list_job_applications`
- **[Send a candidate shortlist to a client](https://cotlet.dev/integrations/vincere-api-mcp-server/send-shortlist-to-client.md)** (runs: weekly): "For job 1042 in Vincere, send the shortlisted candidates to the client as a LiveList with attachments, names visible. Show me the list before you send." → `list_job_applications`, `get_candidate`, `send_candidates_to_client`
- **[Log call notes and follow-up tasks](https://cotlet.dev/integrations/vincere-api-mcp-server/log-calls-and-follow-up-tasks.md)** (runs: daily): "Log this call on Priya Nair in Vincere as an outbound connected call with these notes, then add a task for me to send her the job description on Friday at 10:00." → `list_candidates`, `list_activities`, `add_comment`, `add_task`
- **Send new jobs to candidates** (runs: weekly): "Send the three newest open jobs in Vincere to candidates in the Java talent pool who are not already on them, with a short personal note." → `list_jobs`, `list_candidates`, `send_job_list_to_candidates`
- **Weekly pipeline report** (runs: weekly): "Every Monday, show me for each of my open jobs how many candidates are in each stage and which jobs have nobody past Shortlisted." → `list_jobs`, `list_job_applications`

## Can Vincere automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Vincere connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to shortlist candidates for a job, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/vincere/jobs. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/vincere/jobs with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 13 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Vincere.

### list_jobs

Jobs of your agency with company, contact, owner, status and sourcing dates. Access: read. REST: `GET /api/v1/vincere/jobs`. MCP: `vincere_read → list_jobs`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | open or closed. Default: all. |
| `query` | string | no | Part of the job title or company name. |
| `limit` | integer | no | How many jobs to return on one page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists jobs as Vincere shows them in the Jobs table, one page at a time; pass next_cursor back as cursor for the next page. status filters open or closed jobs. query matches the job title or company name. Use job_id from here in the other tools. Only open jobs can take new shortlists.

Example response:

```json
{
  "jobs": [
    {
      "job_id": "1042",
      "title": "Senior Java Developer",
      "company": "Brightline Tech",
      "contact": "Alex Reed",
      "owner": "Dana Fox",
      "status": "open",
      "job_type": "Permanent",
      "sourcing_close_date": "2026-11-30"
    },
    {
      "job_id": "1047",
      "title": "Data Engineer",
      "company": "Northwind Systems",
      "contact": "Sam Okafor",
      "owner": "Dana Fox",
      "status": "open",
      "job_type": "Contract",
      "sourcing_close_date": "2026-12-15"
    }
  ],
  "next_cursor": null
}
```

### get_job

One job with its details, public and internal description and brief notes. Access: read. REST: `GET /api/v1/vincere/jobs/{job_id}`. MCP: `vincere_read → get_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job id from list_jobs. |

Returns the fields of the Job Quick View: location, owner, category, sourcing open and close dates, employment type, industry, the public and internal description and the brief notes. Read sourcing_close_date before shortlisting, because Vincere offers only open jobs with headcount and a sourcing date that has not passed.

Example response:

```json
{
  "job_id": "1042",
  "title": "Senior Java Developer",
  "company": "Brightline Tech",
  "status": "open",
  "location": "London",
  "owner": "Dana Fox",
  "category": "Technology",
  "employment_type": "Permanent",
  "sourcing_open_date": "2026-10-05",
  "sourcing_close_date": "2026-11-30",
  "public_description": "Build and run payment services in Java for a growing fintech team.",
  "internal_description": "Client wants 5+ years of Java. Rate discussed on the last call.",
  "brief": [
    {
      "title": "Client call",
      "note": "Prefers candidates who can start in January."
    }
  ]
}
```

### list_candidates

Candidates of your agency or of one Talent Pool, with title, company and owner. Access: read. REST: `GET /api/v1/vincere/candidates`. MCP: `vincere_read → list_candidates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `talent_pool` | string | no | Name of a Talent Pool to list. |
| `query` | string | no | Part of the candidate name. |
| `limit` | integer | no | How many candidates to return on one page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists candidates as the Candidates table shows them, one page at a time; pass next_cursor back as cursor for the next page. talent_pool takes the name of a Talent Pool. query matches the candidate name. Use candidate_id from here in get_candidate, shortlist_candidates and add_comment.

Example response:

```json
{
  "candidates": [
    {
      "candidate_id": "88214",
      "name": "Priya Nair",
      "job_title": "Java Developer",
      "current_company": "Northwind Systems",
      "owner": "Dana Fox"
    },
    {
      "candidate_id": "88230",
      "name": "Tomas Wu",
      "job_title": "Project Manager",
      "current_company": "Harbor Labs",
      "owner": "Dana Fox"
    }
  ],
  "next_cursor": null
}
```

### get_candidate

One candidate with title, company, owner, Talent Pools and applications with their stage. Access: read. REST: `GET /api/v1/vincere/candidates/{candidate_id}`. MCP: `vincere_read → get_candidate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | yes | Candidate id from list_candidates. |

Returns the profile of one candidate: current job title and company, owner, the Talent Pools they are in and every application with its job and stage. Check applications before shortlisting, because Vincere counts shortlisted, floated and applied positions toward 1,000 per candidate.

Example response:

```json
{
  "candidate_id": "88214",
  "name": "Priya Nair",
  "job_title": "Java Developer",
  "current_company": "Northwind Systems",
  "owner": "Dana Fox",
  "talent_pools": [
    "Java"
  ],
  "applications": [
    {
      "job_id": "1047",
      "job_title": "Data Engineer",
      "stage": "Applications"
    }
  ]
}
```

### list_job_applications

Candidates on one job with their pipeline stage. Access: read. REST: `GET /api/v1/vincere/job-applications`. MCP: `vincere_read → list_job_applications`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job id from list_jobs. |
| `stage` | enum | no | applications, shortlisted, sent, first_interview, second_plus_interview, offer or placed. Default: all. |
| `limit` | integer | no | How many applications to return on one page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the candidates of one job with the stage each is in: applications, shortlisted, sent, first_interview, second_plus_interview, offer or placed. stage keeps one stage. Pass next_cursor back as cursor for the next page. Use it to see who is already on a job and to check that a shortlist or send saved.

Example response:

```json
{
  "applications": [
    {
      "candidate_id": "88214",
      "name": "Priya Nair",
      "stage": "shortlisted"
    },
    {
      "candidate_id": "88230",
      "name": "Tomas Wu",
      "stage": "shortlisted"
    },
    {
      "candidate_id": "88251",
      "name": "Lena Ortiz",
      "stage": "sent"
    }
  ],
  "next_cursor": null
}
```

### list_tasks

Vincere tasks assigned to you, created by you or followed by you, with due date and status. Access: read. REST: `GET /api/v1/vincere/tasks`. MCP: `vincere_read → list_tasks`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `scope` | enum | no | assigned_to_me, created_by_me or following. Default: assigned_to_me. |
| `status` | enum | no | outstanding, overdue or completed. Default: all. |
| `limit` | integer | no | How many tasks to return on one page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists tasks as the Task board shows them. scope picks the section: assigned_to_me, created_by_me or following. status keeps outstanding, overdue or completed tasks. Each task has its subject, type, due date and time, assignee and the record it is linked to.

Example response:

```json
{
  "tasks": [
    {
      "task_id": "T-5521",
      "subject": "Send Priya the job description",
      "type": "Candidate",
      "due": "2026-10-23T10:00:00",
      "assignee": "Dana Fox",
      "status": "outstanding",
      "candidate_id": "88214"
    }
  ],
  "next_cursor": null
}
```

### list_activities

Comments, meetings and tasks logged on a candidate or a job, with who added them and when. Access: read. REST: `GET /api/v1/vincere/activities`. MCP: `vincere_read → list_activities`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | no | Candidate id from list_candidates. Use this or job_id. |
| `job_id` | string | no | Job id from list_jobs. Use this or candidate_id. |
| `limit` | integer | no | How many activities to return on one page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the Activities tab of one record: comments, meetings and tasks with the Action, the notes, the person who logged them and the time. Pass candidate_id or job_id, one of the two. Read it before add_comment so a call is not logged twice.

Example response:

```json
{
  "activities": [
    {
      "type": "comment",
      "action": "Phone call | Candidate | Outbound | Connected",
      "notes": "Intro call, interested in contract work.",
      "by": "Dana Fox",
      "at": "2026-10-20T15:12:00"
    }
  ],
  "next_cursor": null
}
```

### add_comment

Log a comment on a candidate with an Action, such as a connected call, and notes. Access: write, asks the user first. REST: `POST /api/v1/vincere/candidates/{candidate_id}/comments`. MCP: `vincere_write → add_comment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | yes | Candidate id from list_candidates. |
| `action` | string | yes | Action name exactly as in the Action dropdown, e.g. "Phone call | Candidate | Outbound | Connected". |
| `notes` | string | yes | The note text. |
| `job_id` | string | no | Link the comment to this job. Needs an active application. |

Adds a comment to the candidate's Activities tab for one candidate. action is the name as it appears in the Action dropdown, and only Actions activated in Goal Console under Activate in Action List are accepted. Only connected calls count toward goals. Pass job_id to link the comment to a job, which works only if the candidate has an active application for it. Colleagues see the comment, and Cotlet has no tool to delete it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "comment_id": "C-90412",
  "candidate_id": "88214",
  "action": "Phone call | Candidate | Outbound | Connected",
  "logged_at": "2026-10-22T16:40:00"
}
```

### add_task

Create a Vincere task with subject, type, due date and assignee. Access: write, asks the user first. REST: `POST /api/v1/vincere/tasks`. MCP: `vincere_write → add_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `subject` | string | yes | Short title of the task. |
| `task_type` | enum | no | candidate, contact, project, job, job_lead or personal. Default: personal. |
| `due` | datetime | yes | Due date and time, ISO 8601. |
| `assignee` | string | no | Team member responsible. Default: you. |
| `candidate_id` | string | no | Link the task to this candidate. |
| `job_id` | string | no | Link the task to this job. |
| `description` | string | no | Longer text of the task. |
| `sync_with_calendar` | boolean | no | Add the task to your connected calendar. Cannot be undone. Default: false. |

Creates a task like the Task board form. task_type is candidate, contact, project, job, job_lead or personal. Pass candidate_id or job_id to link it. The assignee is notified in Vincere. With sync_with_calendar true the task goes to your primary connected calendar, and once synced it cannot be un-synced. Cotlet has no tool to delete a task. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "task_id": "T-5521",
  "subject": "Send Priya the job description",
  "type": "Candidate",
  "due": "2026-10-23T10:00:00",
  "assignee": "Dana Fox",
  "calendar_synced": false
}
```

### shortlist_candidates

Shortlist candidates to an open job. Access: write, asks the user first. REST: `POST /api/v1/vincere/jobs/{job_id}/candidates/shortlist`. MCP: `vincere_write → shortlist_candidates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job id from list_jobs. The job must be open. |
| `candidate_ids` | array | yes | Candidate ids from list_candidates, up to 300. |

Moves the candidates to the Shortlisted stage of one open job, like Shortlist in the Candidates table. It sends nothing to the candidates or the client. A closed job, a job with no headcount left or a passed Sourcing closed date is refused, and the candidates are returned in skipped with the reason. Vincere allows 300 selected records at once. Moving a candidate back needs Remove Application in Vincere. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_id": "1042",
  "shortlisted": [
    {
      "candidate_id": "88214",
      "name": "Priya Nair",
      "stage": "shortlisted"
    },
    {
      "candidate_id": "88230",
      "name": "Tomas Wu",
      "stage": "shortlisted"
    }
  ],
  "skipped": []
}
```

### send_candidates_to_client

Email candidates to the client as a LiveList for a job and move them to Sent. Access: write, asks the user first. REST: `POST /api/v1/vincere/jobs/{job_id}/candidates-to-clients`. MCP: `vincere_write → send_candidates_to_client`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job id from list_jobs. |
| `candidate_ids` | array | yes | Candidate ids on that job, from list_job_applications. |
| `include_attachments` | boolean | no | Attach the candidates' documents. Default: false. |
| `hide_names` | boolean | no | Hide candidate names and current employers from the client. Default: false. |
| `message` | string | no | Replaces the body of the email template. |
| `extra_recipients` | array | no | Email addresses to add to the job contact. |

Sends a LiveList for one job to its client, using Vincere's template 2.5 Send Candidate List, and moves the applications to the Sent stage. hide_names hides candidate names and current employers. message replaces the email body and extra_recipients adds addresses. Vincere limits one email action to 100 recipients. The email reaches the client and cannot be recalled. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_id": "1042",
  "sent": [
    {
      "candidate_id": "88214",
      "name": "Priya Nair",
      "stage": "sent"
    },
    {
      "candidate_id": "88230",
      "name": "Tomas Wu",
      "stage": "sent"
    },
    {
      "candidate_id": "88251",
      "name": "Lena Ortiz",
      "stage": "sent"
    }
  ],
  "template": "2.5 - Send Candidate List",
  "recipients": [
    "alex.reed@brightline.example"
  ],
  "names_visible": true,
  "attachments_included": true
}
```

### send_job_list_to_candidates

Email a list of jobs to candidates, who can accept or decline each role. Access: write, asks the user first. REST: `POST /api/v1/vincere/job-list-to-candidates`. MCP: `vincere_write → send_job_list_to_candidates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_ids` | array | yes | Job ids from list_jobs, up to 10. |
| `candidate_ids` | array | yes | Candidate ids from list_candidates, up to 100. |
| `message` | string | no | Personal note added to the email. |

Sends up to 10 jobs to up to 100 candidates, like Send Job List to Candidates in Vincere. Closed jobs, candidates with a company exclusion notice and candidates already in process for a job are dropped and returned in skipped. Candidates get a branded email and a page where they accept or reject each role, and the Job Consent column tracks it. The email reaches candidates and cannot be recalled. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "sent": 2,
  "jobs": [
    "1042",
    "1047"
  ],
  "candidates": [
    "88214",
    "88251"
  ],
  "skipped": [
    {
      "candidate_id": "88230",
      "reason": "already in the process for job 1047"
    }
  ],
  "job_consent": "Pending"
}
```

### move_application_stage

Move a candidate to the next stage of a job without sending an email. Access: write, asks the user first. REST: `POST /api/v1/vincere/jobs/{job_id}/application-stage/move`. MCP: `vincere_write → move_application_stage`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job id from list_jobs. |
| `candidate_id` | string | yes | Candidate id from list_job_applications. |
| `stage` | enum | yes | sent, first_interview, second_plus_interview or offer. |

Does what Move to next stage does in Vincere: stage is sent, first_interview, second_plus_interview or offer. It sends no email to the client or the candidate. Vincere does not move a candidate backward, and an offer can need approval first, so it comes back as pending_approval. Placing a candidate stays in Vincere, because it needs the placement details page. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_id": "1042",
  "candidate_id": "88251",
  "from_stage": "sent",
  "stage": "first_interview",
  "emailed": false
}
```

## How do I connect Vincere to Claude Code, Codex or Cursor?

Connecting Vincere takes three steps: sign up, sign in to Vincere once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Vincere to your agent.

1. **Create an account** Sign up and add Vincere in the console. Your API key is there too.

2. **Sign in to Vincere in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Vincere there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Vincere tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
For the open job "Senior Java Developer" in Vincere, find candidates in the Java talent pool, skip anyone already on that job, and shortlist the ones whose current title is a developer role. List the rest for me.
```

### Call Vincere from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/vincere with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/vincere/jobs/1042/candidates/shortlist \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"candidate_ids":["88214","88230"]}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "job_id": "1042",
  "shortlisted": [
    {
      "candidate_id": "88214",
      "name": "Priya Nair",
      "stage": "shortlisted"
    },
    {
      "candidate_id": "88230",
      "name": "Tomas Wu",
      "stage": "shortlisted"
    }
  ],
  "skipped": []
}
```

## Why use Cotlet for Vincere?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Vincere yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Vincere changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Vincere to Cotlet?

Yes. You sign in to Vincere yourself, in your own Cloud Browser, and we never save your password. Your agents only get Vincere once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Vincere integration?**

No, Cotlet is independent of Vincere. Vincere's own API is open only to approved partners. Cotlet works through your own Vincere account, the way you use Vincere in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Vincere in your console: your agents lose access at once and you stay signed in. Signing out of Vincere in the browser works too, and Reset browser deletes the whole profile.

## Is there a Vincere MCP server on GitHub?

Zapier has a Vincere app, and Vincere lists it as a partner. It covers new-candidate, new-job and new-placement triggers and VinnyChat messages, and setup needs an API key from Vincere Support. It has no action to shortlist, send a LiveList, move a stage, log a comment or add a task. Cotlet works in your signed-in Vincere account and does those jobs, hosted.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Ask Vincere Support for an API key with your tenant URL, then connect your login in Zapier | Sign up, sign in to Vincere once, add one MCP server or API key |
| What it does | Fires on new candidates, jobs and placements; sends VinnyChat messages; adds a contact; unsubscribes an email | Shortlists, sends LiveLists and job lists, moves stages, logs comments, adds tasks, reads jobs and candidates |
| When Vincere changes | The Zapier app is kept up by its publisher | Our team tests it daily and fixes it for you; failed calls are free |
| Your Vincere session | API key and login stored in Zapier | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | Runs on the key Vincere issued | Your Cloud Browser keeps you signed in; if Vincere logs you out, your agent gets a link to sign in again |
| Where it runs | Zaps in Zapier, started by Vincere events | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | A Zapier plan | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Vincere changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Vincere API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Vincere API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Vincere account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Vincere yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Vincere only after you enable it. When Vincere signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Vincere, sign out of Vincere in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Vincere's terms:** You use your own Vincere account and stay responsible for following Vincere's terms. Cotlet is independent and not affiliated with Vincere. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Vincere in the console and press Request access. Then you create your API key and connect Vincere there.

**Do I need to be technical?**

No. You sign in to Vincere once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Vincere to Cotlet?**

Yes. You sign in to Vincere yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Vincere once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Vincere sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Vincere cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Vincere's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Vincere sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Vincere login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Vincere offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Which Vincere role does my account need?**

Cotlet works in your own Vincere login and sees what you see. Shortlisting needs a user account with the permission for it, and a company that is compliant, according to Vincere's Help Center, which names no role. Logging a call as a comment needs the call Action activated in Settings > Goal Console, and an admin with access to Settings and Goal Console does that.

**Which tools send email?**

Two do: send_candidates_to_client emails the client a LiveList, and send_job_list_to_candidates emails candidates a job list. Vincere limits an email action to 100 recipients, and a job-list send to 10 jobs and 100 candidates. shortlist_candidates and move_application_stage send nothing. Each write waits for your OK by default.

**What does it not cover?**

Placements stay in Vincere: Place opens the placement details page and Vincere runs compliance checks on it. A candidate cannot be moved back a stage, merged, archived or removed from a job through these tools, and Float to Contact for a role with no open job is not built. Comments and tasks cannot be deleted through Cotlet. Vincere also limits a candidate to 1,000 position associations.

**Can my agent post or send messages in Vincere without asking me?**

No. Every call to add_comment, add_task, shortlist_candidates, send_candidates_to_client, send_job_list_to_candidates or move_application_stage waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Vincere API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/vincere from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.