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

# Yousign API and MCP server

> Yousign has a full REST API (v3) but sells it only on separate API plans, and its official AI connector is narrow (checked 20 Oct 2026). The API plans start at 104 EUR a month excl. VAT, billed yearly, with a free 40-day sandbox for testing. The AI connector works on all plans and can send a signature request from an existing template, list pending requests and check whether a person has signed. It has no reminders, cancelling or downloads.

E-signature platform, now branded Youtrust, where you send documents to signers by email and follow each request until everyone has signed, with templates, reminders and audit trails.

## What is the Yousign API?

Cotlet's Yousign API exposes 11 endpoints for your own Yousign account: list signature requests, get signature request, list templates, list contacts, download signed documents, download audit trail, create signature request from template, send signature request, send reminder, cancel signature request and create contact. The list_signature_requests endpoint returns lists signature requests with their status and signers. Each endpoint takes simple JSON inputs like signature_request_id, signer_id or status and works both as an operation of the yousign_read or yousign_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Productivity & teams](https://cotlet.dev/integrations/category/productivity-teams.md)
- **Endpoints:** 11 (6 read, 5 write)
- **Updated:** 2026-10-19

Yousign has a full REST API (v3) but sells it only on separate API plans, and its official AI connector is narrow (checked 20 Oct 2026). Cotlet is a hosted MCP server and REST API for Yousign with 11 endpoints (6 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Yousign have an official API?

Yousign has a full REST API (v3) but sells it only on separate API plans, and its official AI connector is narrow (checked 20 Oct 2026). The API plans start at 104 EUR a month excl. VAT, billed yearly, with a free 40-day sandbox for testing. The AI connector works on all plans and can send a signature request from an existing template, list pending requests and check whether a person has signed. It has no reminders, cancelling or downloads.

| Task | Yousign official | Cotlet |
|---|---|---|
| List signature requests and read their status | Yes: API plans; the AI connector lists pending requests | Yes |
| Check whether a signer has signed | Yes: API plans and the AI connector | Yes |
| Create a request from a template and send it | Yes: API plans; the AI connector sends from an existing template on all plans | Yes |
| Send a reminder to signers | Partly: API plans only; not in the AI connector | Yes |
| Cancel a signature request | Partly: API plans only; not in the AI connector | Yes |
| Download signed documents | Partly: API plans only; not in the AI connector | Yes |
| Download audit trails | Partly: API plans only; not in the AI connector | Yes |
| Create a contact | Partly: API plans only | Yes |

Sources: [Youtrust (Yousign): API pricing](https://youtrust.com/pricing-api), [Youtrust (Yousign): AI connector](https://youtrust.com/ai-connector), [Yousign developers: Create your first signature request](https://developers.youtrust.com/docs/create-your-first-signature-request), [Yousign Help: Create a signature request](https://help.youtrust.com/en/articles/71619-create-a-signature-request)

## For AI agents

```text
Yousign has a full REST API (v3) but sells it only on separate API plans, and its official AI connector is narrow (checked 20 Oct 2026). The API plans start at 104 EUR a month excl. VAT, billed yearly, with a free 40-day sandbox for testing. The AI connector works on all plans and can send a signature request from an existing template, list pending requests and check whether a person has signed. It has no reminders, cancelling or downloads.
Cotlet provides a hosted MCP server and REST API for Yousign: 11 tools (6 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=yousign, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    yousign_read, yousign_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/yousign, each operation at its own route, e.g. POST /api/v1/yousign/signature-requests/{signature_request_id}/reminders
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_signature_requests, get_signature_request, list_templates, list_contacts, download_signed_documents, download_audit_trail, create_signature_request, send_signature_request, send_reminder, cancel_signature_request, create_contact
Confirm      send_signature_request, send_reminder, cancel_signature_request (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/yousign-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=yousign, requests Yousign in the Cotlet console and creates an API key there.
2. The user signs in to Yousign once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Yousign 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 Yousign server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Yousign MCP server instead.

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 Yousign 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 Yousign 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 Yousign 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 Yousign's terms; Cotlet is not affiliated with Yousign.
```

## What can an AI agent do in Yousign?

Cotlet is best for teams and freelancers on a normal Yousign plan who want their AI agent to send contracts from templates, chase unsigned requests and file signed documents without running or fixing a server.

- **[Send contracts from a template](https://cotlet.dev/integrations/yousign-api-mcp-server/send-contracts-from-template.md)**: "Take the Freelance agreement template, create a request for ana@example.com as Contractor, show me the draft and send it after I say OK." → `list_templates`, `create_signature_request`, `send_signature_request`
- **[Chase unsigned signature requests](https://cotlet.dev/integrations/yousign-api-mcp-server/chase-unsigned-signature-requests.md)** (runs: daily): "List my signature requests still In progress, tell me who has not signed, and send a reminder to those signers." → `list_signature_requests`, `get_signature_request`, `send_reminder`
- **[File signed documents and audit trails](https://cotlet.dev/integrations/yousign-api-mcp-server/archive-signed-documents.md)** (runs: daily): "Find signature requests completed since yesterday and download each signed document and its audit trail." → `list_signature_requests`, `download_signed_documents`, `download_audit_trail`
- **Cancel outdated signature requests**: "Cancel the In progress request named Lease renewal with the reason that the terms changed, and tell the signers." → `list_signature_requests`, `cancel_signature_request`
- **Weekly signature status report** (runs: weekly): "Every Monday, tell me which signature requests are still waiting and on whom." → `list_signature_requests`, `get_signature_request`

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

Yes. Cotlet does not replace your automation platform: it gives it a Yousign 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 chase unsigned signature requests, 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/yousign/signature-requests. | 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/yousign/signature-requests with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 11 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 Yousign.

### list_signature_requests

Lists signature requests with their status and signers. Access: read. REST: `GET /api/v1/yousign/signature-requests`. MCP: `yousign_read → list_signature_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | Only requests with this status, as the Signatures page shows it, for example In progress or Completed. Leave out for all. |

Returns each request with its ID, name, status, creation date and a signer count. Requests come as the Signatures page lists them. Any role in the workspace can read the list it can see in the app.

Example response:

```json
{
  "signature_requests": [
    {
      "id": "8c1d4e7a-52b9-4f03-a6d8-91e0b3c5f274",
      "name": "Service agreement",
      "status": "In progress",
      "created_at": "2026-10-14T09:12:00Z",
      "signers": 3,
      "signed": 1
    },
    {
      "id": "2a7f9e10-3b4c-4d85-a6e1-7c90d2b8f351",
      "name": "Lease renewal",
      "status": "In progress",
      "created_at": "2026-10-19T14:40:00Z",
      "signers": 2,
      "signed": 1
    }
  ]
}
```

### get_signature_request

Returns one request with its signers, documents and settings. Access: read. REST: `GET /api/v1/yousign/signature-requests/{signature_request_id}`. MCP: `yousign_read → get_signature_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `signature_request_id` | string | yes | Signature request ID from list_signature_requests or create_signature_request. |

Returns the status, expiration date, each signer with name, email and status, and the documents. Use it to see who has not signed. A request in Draft shows no signer progress yet.

Example response:

```json
{
  "id": "8c1d4e7a-52b9-4f03-a6d8-91e0b3c5f274",
  "name": "Service agreement",
  "status": "In progress",
  "expires_at": "2027-04-14",
  "signers": [
    {
      "id": "b7e2a9d4-1c63-4a58-8f0e-d35c6a41b2f9",
      "name": "Tom Becker",
      "email": "tom@example.com",
      "status": "Notified"
    },
    {
      "id": "e41c8d70-9a2b-4f6e-b153-6d0a7c2e98f4",
      "name": "Maya Chen",
      "email": "maya@example.com",
      "status": "Signed"
    },
    {
      "id": "0f93b6d2-4e17-4a8c-95d1-a8e3c7b02f65",
      "name": "Lena Ortiz",
      "email": "lena@example.com",
      "status": "Notified"
    }
  ],
  "documents": [
    {
      "name": "Service agreement.pdf"
    }
  ]
}
```

### list_templates

Lists the templates you can create signature requests from. Access: read. REST: `GET /api/v1/yousign/templates`. MCP: `yousign_read → list_templates`.

No parameters.

Returns each template with its ID, name, status and the role names of its placeholder signers. Only templates in Active status can start a request. Templates are made in the Yousign app, not here.

Example response:

```json
{
  "templates": [
    {
      "id": "a1b2c3d4-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
      "name": "Freelance agreement",
      "status": "Active",
      "placeholder_signers": [
        "Contractor"
      ]
    },
    {
      "id": "f0e9d8c7-b6a5-4948-8372-6150a4b3c2d1",
      "name": "NDA",
      "status": "Active",
      "placeholder_signers": [
        "Counterparty"
      ]
    }
  ]
}
```

### list_contacts

Lists the contacts in your Yousign contact book. Access: read. REST: `GET /api/v1/yousign/contacts`. MCP: `yousign_read → list_contacts`.

No parameters.

Returns each contact with name, email and company. Use it to reuse a saved signer instead of typing details again.

Example response:

```json
{
  "contacts": [
    {
      "id": "c8d7e6f5-a4b3-4c2d-9e1f-0a9b8c7d6e5f",
      "first_name": "Ana",
      "last_name": "Lopez",
      "email": "ana@example.com",
      "company": "Lopez Studio"
    }
  ]
}
```

### download_signed_documents

Returns the signed documents of a request as a file link. Access: read. REST: `GET /api/v1/yousign/signature-requests/{signature_request_id}/signed-documents/download`. MCP: `yousign_read → download_signed_documents`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `signature_request_id` | string | yes | Signature request ID from list_signature_requests or create_signature_request. |

Returns the file name, size and a download URL: a PDF for one document, a zip for several documents or attachments. A completed request carries "(signed)" in the file name. A request that is still In progress returns the documents as they are now.

Example response:

```json
{
  "file_name": "Service agreement (signed).pdf",
  "size_bytes": 184320,
  "download_url": "https://files.cotlet.dev/d/Q3x9Lk2mVw"
}
```

### download_audit_trail

Returns the proof file of a request or of one signer. Access: read. REST: `GET /api/v1/yousign/signature-requests/{signature_request_id}/audit-trails/download`. MCP: `yousign_read → download_audit_trail`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `signature_request_id` | string | yes | Signature request ID from list_signature_requests or create_signature_request. |
| `signer_id` | string | no | Signer ID from get_signature_request. Leave out for the whole request, which works for a completed request. |

Returns a zip with one audit trail per signer for a completed request, or the PDF of one signer who has already signed. The audit trail holds the signer details, the authentication method, the signing context and the hash of the signed PDF. It needs a user with access to the request.

Example response:

```json
{
  "file_name": "Service agreement audit trails.zip",
  "signers": 3,
  "size_bytes": 412672,
  "download_url": "https://files.cotlet.dev/d/Hn4Zp7tRcB"
}
```

### create_signature_request

Creates a draft signature request from an Active template. Access: write. REST: `POST /api/v1/yousign/templates/{template_id}/signature-requests`. MCP: `yousign_write → create_signature_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `template_id` | string | yes | Template ID from list_templates. The template must be Active. |
| `name` | string | no | Name of the request. Leave out to use the template name. |
| `signers` | array | yes | One object per placeholder signer: role (the role name in the template), first_name, last_name, email. |
| `text_fields` | object | no | Values for the empty Read-only Text fields of the template, keyed by field name. |

Returns the draft with its ID, signers and filled fields. It fails when a placeholder role has no signer or a Read-only Text field is still empty. The draft reaches no one: signers are emailed only when you call send_signature_request, so this tool does not ask for confirmation.

Example response:

```json
{
  "id": "3f6b1c2e-8a41-4d7c-9b5e-2a0f6d1c7e90",
  "name": "Freelance agreement",
  "status": "Draft",
  "signers": [
    {
      "role": "Contractor",
      "name": "Ana Lopez",
      "email": "ana@example.com"
    }
  ],
  "text_fields": {
    "monthly_fee": "2,400 EUR"
  }
}
```

### send_signature_request

Sends a draft to its signers. Access: write, asks the user first. REST: `POST /api/v1/yousign/signature-requests/{signature_request_id}`. MCP: `yousign_write → send_signature_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `signature_request_id` | string | yes | Signature request ID from list_signature_requests or create_signature_request. |

Moves a request from Draft to In progress and Yousign emails each signer an invitation. With a signing order set, only the first signer is invited at once. A request that is not in Draft fails. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "id": "3f6b1c2e-8a41-4d7c-9b5e-2a0f6d1c7e90",
  "name": "Freelance agreement",
  "status": "In progress",
  "invited": 1
}
```

### send_reminder

Reminds signers who have not signed yet. Access: write, asks the user first. REST: `POST /api/v1/yousign/signature-requests/{signature_request_id}/reminders`. MCP: `yousign_write → send_reminder`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `signature_request_id` | string | yes | Signature request ID from list_signature_requests or create_signature_request. |
| `signer_id` | string | no | Signer ID from get_signature_request. Leave out to act on every recipient who still has to sign. |

Sends the reminder email for a request that is In progress, to one signer or to every recipient whose signature is pending. With a signing order set, only the signer whose turn it is gets one. Signers who have signed or were not notified yet are skipped and listed. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "signature_request_id": "8c1d4e7a-52b9-4f03-a6d8-91e0b3c5f274",
  "reminded": [
    {
      "name": "Tom Becker",
      "email": "tom@example.com"
    }
  ],
  "skipped": []
}
```

### cancel_signature_request

Cancels a request that is waiting for signatures. Access: write, asks the user first. REST: `POST /api/v1/yousign/signature-requests/{signature_request_id}/cancel`. MCP: `yousign_write → cancel_signature_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `signature_request_id` | string | yes | Signature request ID from list_signature_requests or create_signature_request. |
| `reason` | string | yes | The reason, chosen from the list Yousign offers under Cancel request. |
| `message` | string | no | Optional custom message shown to the signers. |

Works on a request in Approval or In progress. Participants are notified and can no longer open the signature page, and a cancelled request cannot be reactivated. The documents stay downloadable and the request can be duplicated. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "id": "2a7f9e10-3b4c-4d85-a6e1-7c90d2b8f351",
  "name": "Lease renewal",
  "status": "Cancelled",
  "reason": "Terms changed",
  "notified": 2
}
```

### create_contact

Adds a contact to your Yousign contact book. Access: write. REST: `POST /api/v1/yousign/contacts`. MCP: `yousign_write → create_contact`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `first_name` | string | yes | First name. |
| `last_name` | string | yes | Last name. |
| `email` | string | yes | Email address. |
| `locale` | string | yes | Language of the contact, for example en or fr. |
| `company_name` | string | no | Company of the contact. |

Returns the new contact with its ID. It notifies no one, and the contact can be removed in the app, so this tool does not ask for confirmation.

Example response:

```json
{
  "id": "c8d7e6f5-a4b3-4c2d-9e1f-0a9b8c7d6e5f",
  "first_name": "Ana",
  "last_name": "Lopez",
  "email": "ana@example.com",
  "locale": "en",
  "company_name": "Lopez Studio"
}
```

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

Connecting Yousign takes three steps: sign up, sign in to Yousign 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 Yousign to your agent.

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

2. **Sign in to Yousign in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Yousign 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 Yousign 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.

```
Take the Freelance agreement template, create a request for ana@example.com as Contractor, show me the draft and send it after I say OK.
```

### Call Yousign 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/yousign 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/yousign/signature-requests/8c1d4e7a-52b9-4f03-a6d8-91e0b3c5f274/reminders \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"signer_id":"b7e2a9d4-1c63-4a58-8f0e-d35c6a41b2f9"}'
```

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

```
{
  "signature_request_id": "8c1d4e7a-52b9-4f03-a6d8-91e0b3c5f274",
  "reminded": [
    {
      "name": "Tom Becker",
      "email": "tom@example.com"
    }
  ],
  "skipped": []
}
```

## Why use Cotlet for Yousign?

**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 Yousign 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 Yousign changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Yousign to Cotlet?

Yes. You sign in to Yousign yourself, in your own Cloud Browser, and we never save your password. Your agents only get Yousign 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 Yousign integration?**

No, Cotlet is independent of Yousign. Yousign's own API is too limited for this work. Cotlet works through your own Yousign account, the way you use Yousign 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 Yousign in your console: your agents lose access at once and you stay signed in. Signing out of Yousign in the browser works too, and Reset browser deletes the whole profile.

## Is there a Yousign MCP server on GitHub?

Yes. Community Yousign MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, give it a Yousign API key, and keep it running yourself; when Yousign changes its API, it stops working until you or the maintainer fix it. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, add your API key, add it to each MCP client | Sign up, sign in to Yousign once, add one MCP server or API key |
| When Yousign changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Yousign access | An API key in a file on your computer, readable by any program you run | Your session 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 | Tools fail until you replace the key by hand | Your Cloud Browser keeps you signed in; if Yousign logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time, plus an API plan for the key | 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 Yousign 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 Yousign API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Yousign 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 Yousign 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 Yousign 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 Yousign only after you enable it. When Yousign 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 Yousign, sign out of Yousign 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.
- **Yousign's terms:** You use your own Yousign account and stay responsible for following Yousign's terms. Cotlet is independent and not affiliated with Yousign. [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 Yousign in the console and press Request access. Then you create your API key and connect Yousign there.

**Do I need to be technical?**

No. You sign in to Yousign 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 Yousign to Cotlet?**

Yes. You sign in to Yousign yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Yousign 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 Yousign 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 Yousign 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 Yousign's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Yousign 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 Yousign 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?**

Yousign 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).

**Do I need a Yousign API plan?**

No. Cotlet works in your own Yousign account, so the separate API plans, from 104 EUR a month excl. VAT billed yearly, are not needed. Your role still counts: templates are created by an owner, administrator or member, and templates are not on the Free plan. You can only see and act on what your account sees in the app.

**Is Yousign now called Youtrust?**

Yes. Yousign pages now redirect to youtrust.com, and the sources on this page use that domain. The app and the API still run under yousign.app. Cotlet works in the same account you already use.

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

No. Every call to send_signature_request, send_reminder or cancel_signature_request waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_signature_request, create_contact runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Yousign 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/yousign 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.