[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)

# Send a Vincere shortlist to a client as a LiveList

> Send shortlisted Vincere candidates to a client as a branded LiveList with your cover note, after you approve the list. Stage moves to Sent.

Source: https://cotlet.dev/integrations/vincere-api-mcp-server/send-shortlist-to-client

The shortlist is ready on Friday, and someone still has to tick the candidates, pick the job, edit the cover email and decide whether the client sees names.

Cotlet does it in your own Vincere account with list\_job\_applications, get\_candidate and send\_candidates\_to\_client, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=vincere) [All Vincere tools](https://cotlet.dev/integrations/vincere-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Vincere do this on its own?

Vincere has no API for this without a partner agreement and no LiveList action in Zapier (checked 22 Oct 2026). The send is a manual list selection in the app, and the cover email is edited each time.

## How you do it in Vincere today

1. The recruiter ticks the candidates in the candidate list, then clicks Actions > Send.
2. In the pop-up the recruiter picks the Job and chooses whether to include attachments.
3. Vincere fills in email template 2.5 - Send Candidate List. The recruiter edits the body, adds recipients and attaches documents.
4. The recruiter chooses whether to show or hide candidate names and current employers, then clicks Send.
5. The client gets an email with a View Candidates button that opens the job's LiveList.
6. For a role with no active job, the recruiter uses Float to Contact, or Float to Distribution List for several recipients.

## How to send a Vincere shortlist to a client as a LiveList

Prompt

```
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.
```

1. 01  
### Read who is ready  
list\_job\_applications with stage shortlisted returns the people waiting on the job. The agent leaves out anyone already at Sent or later, so a client never gets the same candidate twice.
2. 02  
### Check each profile  
get\_candidate shows current title, company and applications. The agent flags a profile with no title or no CV on file and asks whether to send it anyway.
3. 03  
### Show you the list  
Before anything is sent, the agent prints the names, the job, the recipient and whether names are shown or hidden. This is the step to catch a wrong job or a client who must not see a current employer.
4. 04  
### Send once  
send\_candidates\_to\_client sends one LiveList per call. It reaches the client, so it waits for your OK by default, and a sent email cannot be recalled through Cotlet.
5. 05  
### Confirm the stage  
Vincere moves the applications to Sent when the LiveList goes out. The agent reads the job again and reports any candidate still in Shortlisted.

### What you get back

Example data

```
Job 1042: Senior Java Developer, client Alex Reed (Brightline Tech)
Shortlisted candidates: 4
Sent 3 as a LiveList, names visible, attachments included
Held back 1: Tomas Wu has no CV on file
Stage after send: Sent (3)
```

### Other ways to ask

- Every Friday, send each client the candidates shortlisted this week for their jobs, and list what you sent.
- Send the LiveList for job 1042 with candidate names and current employers hidden.
- Draft the LiveList cover note for each open job and wait for my OK before sending.

## What Vincere allows, and what to know first

- Vincere limits email actions to 100 recipients per send, and a candidate selection holds up to 300 records.
- Vincere lets clients on a LiveList rate candidates, start interviews, reject candidates or mark them KIV, and message the recruiter.
- Vincere keeps a rejected candidate visible in the LiveList with a rejected status, and the application has to be deleted from the job to remove them completely.
- Vincere takes the LiveList columns from Admin Settings > LiveList Settings, and they can be changed per job in Job LiveList Settings.
- Vincere updates the pipeline stage when a LiveList is sent, and a candidate can also be moved to Sent without an email by moving the stage by hand.

send\_candidates\_to\_client asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.

Sources: [Vincere Help: Candidate LiveList](https://help.vincere.io/en/articles/1896488-candidate-livelist) · [Vincere Help: Moving candidates down the Pipeline](https://help.vincere.io/en/articles/2601266-moving-candidates-down-the-pipeline) · [Vincere Help: Candidate Actions](https://help.vincere.io/en/articles/11143948-candidate-actions)

## Call send\_candidates\_to\_client from a script

curl

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

Example response

```
{
"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
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is vincere\_write → send\_candidates\_to\_client. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/vincere-api-mcp-server.md#automations)

## Vincere tools this automation uses

__Cotlet Vincere tools used to send a Vincere shortlist to a client as a LiveList__
| Tool | Parameters |
| ---------------------------- | -------------------------------------------------------------------------------------- |
| list\_job\_applications | job\_id, stage, limit, cursor |
| get\_candidate | candidate\_id |
| send\_candidates\_to\_client | job\_id, candidate\_ids, include\_attachments, hide\_names, message, extra\_recipients |

[All 13 Vincere tools with descriptions](https://cotlet.dev/integrations/vincere-api-mcp-server.md#tools)

## Frequently asked questions

### 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.

## More Vincere automations

- [Shortlist Vincere candidates for a job with AI](https://cotlet.dev/integrations/vincere-api-mcp-server/shortlist-candidates-for-a-job.md)
- [Log Vincere call notes and follow-up tasks with AI](https://cotlet.dev/integrations/vincere-api-mcp-server/log-calls-and-follow-up-tasks.md)
- [Vincere API and MCP server: every tool](https://cotlet.dev/integrations/vincere-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Vincere.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Vincere.

[Sign up free](https://cotlet.dev/app/signup?app=vincere)

---

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.