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

# Bizneo API and MCP server

> Yes, Bizneo has a documented REST API, HCM API v1 (checked 22 Oct 2026). It needs a token created in the app, and Bizneo says its API is available as an add-on. The API can request, list and delete absences and log time, but it has no endpoint to approve or reject an absence or a remote work request, and Bizneo has no official MCP server.

HR suite from Madrid for absences and vacations, time tracking, shifts, payroll preparation, onboarding and recruiting, used through a web portal and a mobile app.

## What is the Bizneo API?

Cotlet's Bizneo API exposes 12 endpoints for your own Bizneo account: list absence requests, get absence balance, list absence types, list team absences, list remote work requests, get my timetable, request absence, cancel absence request, approve absence request, reject absence request, request remote work and decide remote work request. The list_absence_requests endpoint returns absence requests with employee, type, dates, state and comment, filtered by state, employee, type or dates. Each endpoint takes simple JSON inputs like start_date, end_date or absence_type and works both as an operation of the bizneo_read or bizneo_write MCP tool for agents and as a REST call for scripts.

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

Yes, Bizneo has a documented REST API, HCM API v1 (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Bizneo with 12 endpoints (6 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Bizneo have an official API?

Yes, Bizneo has a documented REST API, HCM API v1 (checked 22 Oct 2026). It needs a token created in the app, and Bizneo says its API is available as an add-on. The API can request, list and delete absences and log time, but it has no endpoint to approve or reject an absence or a remote work request, and Bizneo has no official MCP server.

| Task | Bizneo official | Cotlet |
|---|---|---|
| Request an absence | Partly: API add-on needed, and the call takes numeric user and absence kind ids | Yes |
| List absence requests and balances | Partly: API add-on needed | Yes |
| Approve or reject an absence request | No | Yes |
| Cancel an absence request | Partly: API can delete an absence, add-on needed | Yes |
| Team absences for a date range | Partly: Absences list filtered by employees, no calendar view | Yes |
| Request remote work | No | Yes |
| Approve or reject remote work requests | No | Yes |
| Read a timetable with approved remote work | Partly: Schedules and timeline lists, add-on needed | Yes |

Sources: [Bizneo HCM API v1](https://connect.bizneo.com/hcm/v1/), [Bizneo: Does it integrate with the tools we already use](https://www.bizneo.com/en/), [Bizneo Help: How to request absences and holidays](https://help.bizneo.com/e-holidays-and-absences/360014841294--Employees-How-to-requests-absences-and-holidays), [Bizneo: Absence and leave management software](https://www.bizneo.com/en/absence-management-software/)

## For AI agents

```text
Yes, Bizneo has a documented REST API, HCM API v1 (checked 22 Oct 2026). It needs a token created in the app, and Bizneo says its API is available as an add-on. The API can request, list and delete absences and log time, but it has no endpoint to approve or reject an absence or a remote work request, and Bizneo has no official MCP server.
Cotlet provides a hosted MCP server and REST API for Bizneo: 12 tools (6 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=bizneo, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    bizneo_read, bizneo_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/bizneo, each operation at its own route, e.g. POST /api/v1/bizneo/absence/request
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_absence_requests, get_absence_balance, list_absence_types, list_team_absences, list_remote_work_requests, get_my_timetable, request_absence, cancel_absence_request, approve_absence_request, reject_absence_request, request_remote_work, decide_remote_work_request
Confirm      request_absence, cancel_absence_request, approve_absence_request, reject_absence_request, request_remote_work, decide_remote_work_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/bizneo-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=bizneo, requests Bizneo in the Cotlet console and creates an API key there.
2. The user signs in to Bizneo once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Bizneo 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 Bizneo 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 Bizneo 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 Bizneo 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 Bizneo 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 Bizneo's terms; Cotlet is not affiliated with Bizneo.
```

## What can an AI agent do in Bizneo?

Cotlet is best for HR managers and team leads who approve absences and remote work in Bizneo and want an AI agent to handle the routine ones without running or fixing a server.

- **[Auto-approve absence requests](https://cotlet.dev/integrations/bizneo-api-mcp-server/auto-approve-absence-requests.md)** (runs: daily): "Go through pending absence requests in Bizneo. Approve vacation of up to 5 days when the balance is enough and at most one teammate is off. Reject requests over the balance with a comment, and leave the rest for me with a one-line reason." → `list_absence_requests`, `get_absence_balance`, `list_team_absences`, `approve_absence_request`, `reject_absence_request`
- **[Request time off from chat](https://cotlet.dev/integrations/bizneo-api-mcp-server/request-time-off-with-ai.md)**: "Request vacation from 21 to 23 December in Bizneo. Check my balance first and warn me if two or more teammates are off on those days." → `list_absence_types`, `get_absence_balance`, `list_team_absences`, `request_absence`
- **[Weekly team absence digest](https://cotlet.dev/integrations/bizneo-api-mcp-server/weekly-team-absence-digest.md)** (runs: weekly): "Every Monday, list who is off this week in Bizneo and which absence requests have waited more than 2 days for a decision." → `list_team_absences`, `list_absence_requests`
- **Request and approve remote work** (runs: weekly): "Request remote work next Tuesday and Thursday, all day. Then approve my team's pending remote work requests that keep each person under 40% of their hours." → `get_my_timetable`, `request_remote_work`, `list_remote_work_requests`, `decide_remote_work_request`

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

Yes. Cotlet does not replace your automation platform: it gives it a Bizneo 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 auto-approve absence 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/bizneo/absence-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/bizneo/absence-requests with your API key. | cron or GitHub Actions. |

## Tools

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

### list_absence_requests

Absence requests with employee, type, dates, state and comment, filtered by state, employee, type or dates. Access: read. REST: `GET /api/v1/bizneo/absence-requests`. MCP: `bizneo_read → list_absence_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `state` | enum | no | pending, approved or rejected. Default: all. |
| `employee` | string | no | Employee name or work email. |
| `absence_type` | string | no | Absence type name as list_absence_types returns it. |
| `start_date` | date | no | Only requests that end on or after this date. |
| `end_date` | date | no | Only requests that start on or before this date. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns one page of absence requests, newest first; pass next_cursor back as cursor for the next page. state is pending, approved or rejected. Without employee you get the requests your account can see: your own, plus your team's for a manager or admin. Each request has a request_id for approve_absence_request, reject_absence_request and cancel_absence_request.

Example response:

```json
{
  "requests": [
    {
      "request_id": "abs_16094565",
      "employee": "Marta Ruiz",
      "absence_type": "Vacation",
      "start_date": "2026-11-09",
      "end_date": "2026-11-13",
      "days": 5,
      "state": "pending",
      "comment": "Family trip",
      "requested_on": "2026-10-20",
      "manager": "Carlos Vega"
    }
  ],
  "next_cursor": null
}
```

### get_absence_balance

What an employee has allotted, taken, waiting and still available for each absence type. Access: read. REST: `GET /api/v1/bizneo/absence-balance`. MCP: `bizneo_read → get_absence_balance`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `employee` | string | no | Employee name or work email. Default: you. |
| `absence_type` | string | no | Absence type name as list_absence_types returns it. Default: all types. |

Returns one row per absence type for the current cycle, in days or hours as the type is set up. pending counts requests that wait for a decision, and available is what is left after taken and pending. Without employee it reads your own balance, the one My Calendar shows. Reading someone else's balance needs a Bizneo role that can see that employee.

Example response:

```json
{
  "employee": "Ana Torres",
  "balances": [
    {
      "absence_type": "Vacation",
      "unit": "days",
      "allotted": 25,
      "taken": 10,
      "pending": 0,
      "available": 15
    },
    {
      "absence_type": "Personal days",
      "unit": "days",
      "allotted": 3,
      "taken": 1,
      "pending": 0,
      "available": 2
    }
  ]
}
```

### list_absence_types

The absence types your company configured, and whether each accepts hours or needs a document. Access: read. REST: `GET /api/v1/bizneo/absence-types`. MCP: `bizneo_read → list_absence_types`.

No parameters.

Returns the types in the Absence type list of the request form, which is what your company set up. allows_hours says whether a request can be for a few hours with a start and an end time. document_required says whether Bizneo asks for a supporting document. needs_approval says whether a manager has to decide. Use the name as absence_type in the other tools.

Example response:

```json
{
  "types": [
    {
      "name": "Vacation",
      "unit": "days",
      "allows_hours": false,
      "document_required": false,
      "needs_approval": true
    },
    {
      "name": "Medical appointment",
      "unit": "hours",
      "allows_hours": true,
      "document_required": true,
      "needs_approval": true
    }
  ]
}
```

### list_team_absences

Absences of colleagues in a date range, with type, dates and state. Access: read. REST: `GET /api/v1/bizneo/team-absences`. MCP: `bizneo_read → list_team_absences`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `start_date` | date | yes | First day of the range. |
| `end_date` | date | yes | Last day of the range. |
| `absence_type` | string | no | Absence type name as list_absence_types returns it. |
| `cursor` | string | no | Next page cursor from the previous call. |

Reads the table behind Absences > My Team, so the account sees the colleagues Bizneo shows it. Returns approved and pending absences that overlap the range, one page at a time; pass next_cursor back as cursor. If your company did not turn on My Team, the call fails with a message saying so.

Example response:

```json
{
  "absences": [
    {
      "employee": "Lucia Fernandez",
      "absence_type": "Vacation",
      "start_date": "2026-10-26",
      "end_date": "2026-10-28",
      "days": 3,
      "state": "approved"
    },
    {
      "employee": "Diego Ramos",
      "absence_type": "Sick leave",
      "start_date": "2026-10-27",
      "end_date": "2026-10-27",
      "days": 1,
      "state": "approved"
    },
    {
      "employee": "Sara Molina",
      "absence_type": "Vacation",
      "start_date": "2026-10-30",
      "end_date": "2026-10-30",
      "days": 1,
      "state": "pending"
    }
  ],
  "next_cursor": null
}
```

### list_remote_work_requests

Remote work requests waiting for a decision or already decided, with employee, day and time. Access: read. REST: `GET /api/v1/bizneo/remote-work-requests`. MCP: `bizneo_read → list_remote_work_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `state` | enum | no | pending, approved or rejected. Default: pending. |
| `employee` | string | no | Employee name or work email. |
| `start_date` | date | no | Only requests for this day or later. |
| `end_date` | date | no | Only requests for this day or earlier. |
| `cursor` | string | no | Next page cursor from the previous call. |

Reads the requests under Time > Requests, which the time manager or the time module admin can see. Returns one page, oldest first; pass next_cursor back as cursor. time is all day or the range the employee set. Pass request_id to decide_remote_work_request.

Example response:

```json
{
  "requests": [
    {
      "request_id": "rw_5521",
      "employee": "Diego Ramos",
      "date": "2026-10-27",
      "time": "all day",
      "state": "pending",
      "comment": "Plumber visit"
    }
  ],
  "next_cursor": null
}
```

### get_my_timetable

Your shifts for a range, with approved and pending remote work and the remote share of your hours. Access: read. REST: `GET /api/v1/bizneo/my-timetable`. MCP: `bizneo_read → get_my_timetable`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `start_date` | date | yes | First day of the range. |
| `end_date` | date | yes | Last day of the range. |

Reads My Timetable. Returns one row per day with the shift, any absence, and remote_work as approved, pending or none. approved_remote_hours and remote_share_percent are the totals Bizneo shows above the table: approved remote hours against the hours expected in the range.

Example response:

```json
{
  "days": [
    {
      "date": "2026-10-26",
      "shift": "09:00-17:00",
      "absence": null,
      "remote_work": "none"
    },
    {
      "date": "2026-10-27",
      "shift": "09:00-17:00",
      "absence": null,
      "remote_work": "approved"
    },
    {
      "date": "2026-10-28",
      "shift": "09:00-17:00",
      "absence": null,
      "remote_work": "none"
    },
    {
      "date": "2026-10-29",
      "shift": "09:00-17:00",
      "absence": null,
      "remote_work": "pending"
    },
    {
      "date": "2026-10-30",
      "shift": "09:00-17:00",
      "absence": null,
      "remote_work": "none"
    }
  ],
  "expected_hours": 40,
  "approved_remote_hours": 8,
  "remote_share_percent": 20
}
```

### request_absence

Sends an absence request to your manager for the dates and type you give. Access: write, asks the user first. REST: `POST /api/v1/bizneo/absence/request`. MCP: `bizneo_write → request_absence`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `absence_type` | string | yes | Absence type name as list_absence_types returns it. |
| `start_date` | date | yes | First day of the absence. |
| `end_date` | date | yes | Last day. The same as start_date for one day. |
| `from_time` | string | no | Start time HH:MM, only for types that accept hours. |
| `to_time` | string | no | End time HH:MM, only for types that accept hours. |
| `comment` | string | no | Comment your manager will see. |

Does what +Request absence does in My Calendar. The request goes to your manager as pending, and the response shows the days counted and the balance that remains. from_time and to_time work only for types that accept hours. Dates that clash with an absence you already have are refused with the reason. Documents are not uploaded through this tool; attach them in Bizneo. Your manager is notified. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "abs_17021100",
  "state": "pending",
  "absence_type": "Vacation",
  "start_date": "2026-12-21",
  "end_date": "2026-12-23",
  "days": 3,
  "manager": "Carlos Vega",
  "balance_after": {
    "available": 12,
    "unit": "days"
  }
}
```

### cancel_absence_request

Deletes one of your absence requests that has not started yet. Access: write, asks the user first. REST: `POST /api/v1/bizneo/requests/{request_id}/absence-request/cancel`. MCP: `bizneo_write → cancel_absence_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_id` | string | yes | request_id from list_absence_requests. |

Deletes a request you made. Bizneo lets an employee change a request only until the absence starts; after that only a manager or admin can, and the call fails with a message saying so. The balance goes back to what it was. Your manager is notified. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "abs_17021100",
  "state": "cancelled"
}
```

### approve_absence_request

Approves a pending absence request, with an optional comment for the employee. Access: write, asks the user first. REST: `POST /api/v1/bizneo/requests/{request_id}/absence-request/approve`. MCP: `bizneo_write → approve_absence_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_id` | string | yes | request_id from list_absence_requests. |
| `comment` | string | no | Comment the employee will see. |

Approves one pending request, as the manager or admin whose account is signed in. Bizneo sets approvers per absence type, with chains and substitute approvers, so a request your account may not decide fails with a message saying so. The employee is notified, and the request shows fully colored on the calendar. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "abs_16094565",
  "employee": "Marta Ruiz",
  "absence_type": "Vacation",
  "start_date": "2026-11-09",
  "end_date": "2026-11-13",
  "days": 5,
  "state": "approved",
  "decided_by": "Carlos Vega",
  "comment": "Covered by Pablo. Enjoy."
}
```

### reject_absence_request

Rejects a pending absence request, with a comment for the employee. Access: write, asks the user first. REST: `POST /api/v1/bizneo/requests/{request_id}/absence-request/reject`. MCP: `bizneo_write → reject_absence_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_id` | string | yes | request_id from list_absence_requests. |
| `comment` | string | no | Reason the employee will see. Required for absence types where the company set it. |

Rejects one pending request, as the manager or admin whose account is signed in. Bizneo lets a company require a reason for some absence types; without one the call fails and says so. Approver rules are the same as for approve_absence_request. The employee is notified. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "abs_16100231",
  "employee": "Nora Keller",
  "absence_type": "Vacation",
  "start_date": "2026-11-02",
  "end_date": "2026-11-13",
  "days": 10,
  "state": "rejected",
  "decided_by": "Carlos Vega",
  "comment": "Over your remaining balance of 6 days."
}
```

### request_remote_work

Asks your manager to let you work remotely on the days you give, all day or in a time range. Access: write, asks the user first. REST: `POST /api/v1/bizneo/remote-work/request`. MCP: `bizneo_write → request_remote_work`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `dates` | array | yes | Days to request, each as YYYY-MM-DD. |
| `from_time` | string | no | Start of the range HH:MM. Leave out for all day. |
| `to_time` | string | no | End of the range HH:MM. Leave out for all day. |
| `project` | string | no | Project to attach to the shift. |
| `comment` | string | no | Comment your manager will see. |

Does what Actions > Request remote work does in My Timetable. Creates one pending request per day. Without from_time and to_time the whole day is requested. Remote work must be enabled for you by an admin. An approval only makes remote work possible; you still register it when you clock in. Your manager is notified. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_ids": [
    "rw_5530",
    "rw_5531"
  ],
  "state": "pending",
  "dates": [
    "2026-10-27",
    "2026-10-29"
  ],
  "time": "all day",
  "manager": "Carlos Vega"
}
```

### decide_remote_work_request

Approves or rejects a pending remote work request. Access: write, asks the user first. REST: `POST /api/v1/bizneo/requests/{request_id}/remote-work-request/decide`. MCP: `bizneo_write → decide_remote_work_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_id` | string | yes | request_id from list_remote_work_requests. |
| `decision` | enum | yes | approve or reject. |

Does what approve or reject does under Time > Requests, for the time manager or the time module admin. The employee is notified, and an approved day shows an icon in My Timetable. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "rw_5521",
  "state": "approved",
  "decided_by": "Carlos Vega"
}
```

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

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

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

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

```
Go through pending absence requests in Bizneo. Approve vacation of up to 5 days when the balance is enough and at most one teammate is off. Reject requests over the balance with a comment, and leave the rest for me with a one-line reason.
```

### Call Bizneo 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/bizneo 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/bizneo/absence/request \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"absence_type":"Vacation","start_date":"2026-12-21","end_date":"2026-12-23","comment":"Christmas week"}'
```

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

```
{
  "request_id": "abs_17021100",
  "state": "pending",
  "absence_type": "Vacation",
  "start_date": "2026-12-21",
  "end_date": "2026-12-23",
  "days": 3,
  "manager": "Carlos Vega",
  "balance_after": {
    "available": 12,
    "unit": "days"
  }
}
```

## Why use Cotlet for Bizneo?

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

## Is it safe to connect Bizneo to Cotlet?

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

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

## Is there a Bizneo MCP server on GitHub?

Bizneo has no official MCP server. You can call its REST API, which is sold as an add-on, or use its Zapier app. Neither approves or rejects an absence. Cotlet works in your signed-in Bizneo account and complements Zapier, n8n and Make.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Connect the Bizneo HR app, then build one Zap per task | Sign up, sign in to Bizneo once, add one MCP server or API key |
| What it can do | Only the actions the Bizneo HR app lists; the official API has no approve or reject for absences | What you do on screen, including approving and rejecting requests |
| Access needed | A token from the Bizneo API add-on, priced in your Bizneo quote | Your normal Bizneo sign-in, no API add-on |
| When Bizneo changes | Stays as the app and the API expose it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Bizneo session | A long-lived API token | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| Where it runs | Zapier, or your own HTTP calls to the API | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | A Zapier plan plus the Bizneo API add-on | 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 Bizneo 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 Bizneo API cost?

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

**Do I need to be technical?**

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

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

Bizneo 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 the Bizneo API add-on?**

No. Cotlet works in your signed-in Bizneo account and does not use the API. Bizneo says its API is available as an add-on and that it gives you the key, so the official route needs a quote first.

**Which Bizneo role does the account need?**

An employee account can request absences and remote work and read its own balance and timetable. Approving needs an account that Bizneo lets decide the request: approvers are set per absence type, and remote work requests are handled by the time manager or the time module admin. A call your role does not allow fails with a message saying so.

**Can it clock me in and out?**

No. Clocking stays in the Bizneo app, kiosk or web clock. request_remote_work only asks for approval, and Bizneo says an approved remote work request makes it possible, but you still register it when you clock in.

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

No. Every call to request_absence, cancel_absence_request, approve_absence_request, reject_absence_request, request_remote_work or decide_remote_work_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.

**Can I use the Bizneo 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/bizneo 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.