[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.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)

# Create your own Vincere API

> Vincere: API keys only by approval, for integrations with a formal agreement. With Cotlet you build your own: do a job once with your AI agent, save it as an endpoint and call it from n8n or code.

Source: https://cotlet.dev/integrations/api/vincere

Vincere: no self-serve API key; Vincere Support issues keys only for integrations with a formal agreement (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Vincere account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in Vincere session and returns only what your login can see.

[Try it free now](https://cotlet.dev/app/signup?app=vincere)

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Vincere. Vincere is a trademark of its owner. If Vincere's own integrations cover what you need, use them first.

curl Node.js Python

curl

```
curl -X POST "https://cotlet.dev/api/v1/custom/candidates-on-job" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"job": "Senior Accountant"}'
```

Node.js

```
const url = "https://cotlet.dev/api/v1/custom/candidates-on-job";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ job: "Senior Accountant" }),
});
const { data } = await res.json();
```

Python

```
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/candidates-on-job",
headers={"Authorization": f"Bearer {key}"},
json={"job": "Senior Accountant"},
)
data = res.json()["data"]
```

Response 200 OK · JSON

```
{
"data": [
{
"candidate": "Dana R.",
"stage": "Shortlisted",
"consultant": "Kate",
"last_moved": "2026-11-17"
},
{
"candidate": "Leo P.",
"stage": "Sent to client",
"consultant": "Kate",
"last_moved": "2026-11-12"
}
]
}
```

01 Build

## How do you build a Vincere endpoint with Cotlet?

1. 01  
yourcompanyname.vincere.io  
Signed in  
### Sign in to Vincere in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
List the candidates on this job with their stage, the consultant and the date they last moved.  
### Do the job once with your agent.  
For example: "List the candidates on this job with their stage, the consultant and the date they last moved."
3. 03  
Save endpoint  
Name  
candidates-on-job  
Input  
job  
Returns  
candidate, stage, consultant, last\_moved  
### Save it as an endpoint.  
Give it a name, choose its inputs, such as a job or a consultant, and the fields it returns.
4. 04  
$ POST /api/v1/custom/candidates-on-job  
200 OK  
### Call it with your Cotlet API key.  
Each endpoint gets its own address, `POST https://cotlet.dev/api/v1/custom/<name>`. You send JSON in and get JSON back, from the same signed-in Vincere session.

02 Endpoints

## Example endpoints you could build for Vincere

Cotlet ships no fixed list of Vincere endpoints. You decide which endpoints you build and what each one returns.

- POST `/api/v1/custom/candidates-on-job`  
### Candidates on a job  
Candidate, stage, consultant and last move for one job
- POST `/api/v1/custom/stalled-jobs`  
### Jobs with no movement  
Open jobs where no candidate moved for a set number of days
- POST `/api/v1/custom/find-candidates`  
### Find candidates  
Candidates matching skills, place and last activity
- POST `/api/v1/custom/placements-for-period`  
### Placements for a period  
Placements per consultant, with client and fee
- POST `/api/v1/custom/add-candidate-note` writes  
### Add a candidate note  
A note saved on a candidate, with its date
- POST `/api/v1/custom/<name>`

A call to an endpoint you built could look like this:

Request

```
curl -X POST "https://cotlet.dev/api/v1/custom/candidates-on-job" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"job": "Senior Accountant"}'
```

The answer is JSON, with your fields under `data`:

Response · 200 OK

```
{
"data": [
{
"candidate": "Dana R.",
"stage": "Shortlisted",
"consultant": "Kate",
"last_moved": "2026-11-17"
},
{
"candidate": "Leo P.",
"stage": "Sent to client",
"consultant": "Kate",
"last_moved": "2026-11-12"
}
]
}
```

When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.

03 Uses

## What can you use your Vincere endpoints for?

- Schedule Cotlet endpoint Slack or email  
### A Monday report in n8n or Make.  
Stalled jobs and shortlists still waiting, sent to each consultant by email or Slack.
- Schedule endpoint Google Sheets  
### A billing sheet.  
Placements and fees for the month pulled into Google Sheets.
- Your portal endpoint candidates  
### A client portal of your own.  
The candidates on a client's jobs, read from Vincere when the client logs in.
- Voice or chat agent endpoint candidate note  
### Your own screening agent.  
A voice or chat agent that saves its call notes on the candidate in Vincere.

04 Access

## What can an endpoint see and change?

An endpoint works in your own Vincere session, so it can read and change only what your Vincere login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.

An endpoint that changes something, such as adding a candidate note, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.

DRY RUN · nothing sent

$ POST /api/v1/custom/add-candidate-note

would POST yourcompanyname.vincere.io/... add a note to Dana R.

`add-candidate-note`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does Vincere have an official API?

Vincere: "API keys are only issued to partners with a formal agreement with Vincere"; keys are requested from Vincere Support, and Vincere's help center shows an administrator calling the API from Make (checked 20 Nov 2026). Vincere has a Zapier app, and Super Users export records to CSV. The full picture with sources: [Does Vincere have an API or MCP server?](https://cotlet.dev/api-status/vincere.md)

Want ChatGPT or Claude to work in Vincere instead of code? See the [Vincere MCP server](https://cotlet.dev/integrations/vincere-api-mcp-server.md).

1/3

Official API

By approval

[Full API & MCP report](https://cotlet.dev/api-status/vincere.md)

06 Pricing

## What does it cost?

per successful call

 10 credits

when a call fails

 0

in the smallest pack

≈ 500 calls

free trial, no card

 7 days

A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.

## Vincere API with Cotlet: questions

### Is this an official Vincere API?

No. Cotlet is independent and not affiliated with Vincere. The endpoints you build run in your own signed-in Vincere account.

### Do I need to code?

Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.

### What happens when Vincere changes its screens?

An endpoint works while Vincere works the way it did when you built it. If Vincere changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.

### How long can a call take?

Up to 90 seconds, and the answer can be up to 1 MB of JSON.

POST /api/v1/custom/<name>

## Build your first Vincere endpoint

Sign in once, do the job with your agent and save it as an endpoint.

[Try it free now](https://cotlet.dev/app/signup?app=vincere)

No card. Takes about 5 minutes.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.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.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

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.
