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

# Quinyx API and MCP server

> Quinyx has a REST API (checked 22 Oct 2026), but no official MCP server, and the API leaves out the manager's daily work: it cannot approve requests, offer shifts, attest hours or publish a schedule. Credentials are generated by someone with access to Account Settings > Integrations credentials, and a developer has to build the integration.

Workforce management software for shift-based teams: scheduling, time and attendance, payroll transfer, people and forecasting, used by managers in the web app and by employees on mobile.

## What is the Quinyx API?

Cotlet's Quinyx API exposes 13 endpoints for your own Quinyx account: list units and sections, list employees, list shifts, list requests waiting for approval, get a request, list punches and their attest status, approve a request, deny a request, offer an unassigned shift, add an absence, create a shift, attest worked hours and publish the schedule. The list_groups endpoint returns list the units and sections your account can reach, with their ids. Each endpoint takes simple JSON inputs like group_id, employee_id or comment and works both as an operation of the quinyx_read or quinyx_write MCP tool for agents and as a REST call for scripts.

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

Quinyx has a REST API (checked 22 Oct 2026), but no official MCP server, and the API leaves out the manager's daily work: it cannot approve requests, offer shifts, attest hours or publish a schedule. Cotlet is a hosted MCP server and REST API for Quinyx with 13 endpoints (6 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Quinyx have an official API?

Quinyx has a REST API (checked 22 Oct 2026), but no official MCP server, and the API leaves out the manager's daily work: it cannot approve requests, offer shifts, attest hours or publish a schedule. Credentials are generated by someone with access to Account Settings > Integrations credentials, and a developer has to build the integration.

| Task | Quinyx official | Cotlet |
|---|---|---|
| Read shifts | Partly: API v3 has a read-only Shift resource (scope schedule:shifts:read) | Yes |
| Add an absence | Partly: API v2 creates and deletes full and part-time absences at unit level, with the Absence scope on the credentials | Yes |
| Create or edit shifts | No | Yes |
| Read the Needs Approval inbox | No: The User API lets an employee submit a leave application, not a manager read requests | Yes |
| Approve or deny absence requests, shift bookings and swaps | No | Yes |
| Offer an unassigned shift to employees | No | Yes |
| Attest worked hours | No | Yes |
| Publish the schedule | No | Yes |

Sources: [Quinyx Developer Portal: API reference](https://developer.quinyx.com/api), [Quinyx Developer Portal: API v3 authentication](https://developer.quinyx.com/api/v3/authentication), [Quinyx Developer Portal: v2 absences](https://developer.quinyx.com/api/v2/absences), [Quinyx Help: Notifications panel](https://help.quinyx.com/help-centre/docs/notifications)

## For AI agents

```text
Quinyx has a REST API (checked 22 Oct 2026), but no official MCP server, and the API leaves out the manager's daily work: it cannot approve requests, offer shifts, attest hours or publish a schedule. Credentials are generated by someone with access to Account Settings > Integrations credentials, and a developer has to build the integration.
Cotlet provides a hosted MCP server and REST API for Quinyx: 13 tools (6 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=quinyx, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    quinyx_read, quinyx_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/quinyx, each operation at its own route, e.g. POST /api/v1/quinyx/shifts/{shift_id}/offer
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_groups, list_employees, list_shifts, list_approval_requests, get_approval_request, list_timesheet_approvals, approve_request, deny_request, offer_shift, add_absence, create_shift, attest_hours, publish_schedule
Confirm      approve_request, deny_request, offer_shift, add_absence, create_shift, attest_hours, publish_schedule (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/quinyx-api-mcp-server.md

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

## What can an AI agent do in Quinyx?

Cotlet is best for Quinyx shift managers who are not developers and want an AI agent to work through absence requests, open shifts and timesheets without running or fixing a server.

- **[Approve absence requests](https://cotlet.dev/integrations/quinyx-api-mcp-server/approve-absence-requests.md)** (runs: daily): "Go through the absence requests waiting for me in Quinyx. Approve those where at least 3 colleagues are still scheduled each day and the shifts can stay open, deny the ones that overlap the stocktake week, and list the rest for me." → `list_approval_requests`, `get_approval_request`, `list_shifts`, `approve_request`, `deny_request`
- **[Offer open shifts to employees](https://cotlet.dev/integrations/quinyx-api-mcp-server/offer-open-shifts.md)** (runs: daily): "List the unassigned shifts in the next 7 days at Harbor Cafe. For each one, offer it to the 3 employees who have no shift that day, with a short comment, and skip shifts that already have a pending offer." → `list_shifts`, `list_employees`, `offer_shift`
- **[Attest worked hours before payroll](https://cotlet.dev/integrations/quinyx-api-mcp-server/attest-worked-hours-before-payroll.md)** (runs: weekly): "For last week at Harbor Cafe, attest the worked hours of employees who already approved their own time and whose punches have no warnings. List everyone else with the reason." → `list_timesheet_approvals`, `attest_hours`
- **Decide shift swaps and bookings** (runs: daily): "Check the shift swap and shift booking requests waiting for me in Quinyx. Approve swaps between people with the same shift type and no warnings, deny bookings that break an agreement, and list the rest." → `list_approval_requests`, `get_approval_request`, `approve_request`, `deny_request`
- **Publish next weeks of the schedule** (runs: weekly): "Every Friday, check that Harbor Cafe has no unassigned shifts in the next 14 days, and if so, publish the schedule until the end of that period." → `list_shifts`, `publish_schedule`

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

Yes. Cotlet does not replace your automation platform: it gives it a Quinyx 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 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/quinyx/approval-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/quinyx/approval-requests with your API key. | cron or GitHub Actions. |

## Tools

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

### list_groups

List the units and sections your account can reach, with their ids. Access: read. REST: `GET /api/v1/quinyx/groups`. MCP: `quinyx_read → list_groups`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of a unit or section name. |

Returns each group with its id, name, type and parent. Type is unit, section or a higher level, and the ids are what the other tools take as group_id. Shifts and absences can be added to units and sections only. The list follows the groups your roles reach in the group selector.

Example response:

```json
{
  "groups": [
    {
      "group_id": "1042",
      "name": "Harbor Cafe",
      "type": "unit",
      "parent_id": "1001"
    },
    {
      "group_id": "1043",
      "name": "Harbor Cafe Kitchen",
      "type": "section",
      "parent_id": "1042"
    }
  ]
}
```

### list_employees

List the people of a unit or section with their status and badge number. Access: read. REST: `GET /api/v1/quinyx/employees`. MCP: `quinyx_read → list_employees`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group_id` | string | no | Unit or section id from list_groups. Defaults to your home unit. |
| `query` | string | no | Part of a name or a badge number. |
| `include_passive` | boolean | no | Include employees with the Passive status. Default false. |

Returns employee_id, name, badge number, status and home unit. Passive employees are left out by default because Quinyx cannot assign a shift to them. The list shows only people your roles let you see.

Example response:

```json
{
  "employees": [
    {
      "employee_id": "3011",
      "name": "Tom Becker",
      "badge_number": "2041",
      "status": "active",
      "home_unit": "Harbor Cafe"
    },
    {
      "employee_id": "3027",
      "name": "Maria Silva",
      "badge_number": "2058",
      "status": "active",
      "home_unit": "Harbor Cafe"
    }
  ]
}
```

### list_shifts

List shifts of a unit or section in a date range, with who works them. Access: read. REST: `GET /api/v1/quinyx/groups/{group_id}/shifts`. MCP: `quinyx_read → list_shifts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group_id` | string | yes | Unit or section id from list_groups. |
| `from` | string | yes | First day, YYYY-MM-DD. |
| `to` | string | yes | Last day, YYYY-MM-DD. |
| `employee_id` | string | no | Only this employee's shifts. |
| `unassigned_only` | boolean | no | Only shifts without an employee. Default false. |

Returns shift_id, employee (null when unassigned), shift type, start, end, breaks and section. A shift with a pending offer has offer_pending set to true. Unassigned shifts in a period that is not published come back too, but cannot be offered.

Example response:

```json
{
  "shifts": [
    {
      "shift_id": "90518",
      "employee": null,
      "shift_type": "Opening",
      "start": "2026-10-30T06:00",
      "end": "2026-10-30T14:00",
      "break_minutes": 30,
      "section": "Harbor Cafe",
      "offer_pending": false
    },
    {
      "shift_id": "90522",
      "employee": "Maria Silva",
      "shift_type": "Opening",
      "start": "2026-10-30T06:00",
      "end": "2026-10-30T14:00",
      "break_minutes": 30,
      "section": "Harbor Cafe",
      "offer_pending": false
    }
  ]
}
```

### list_approval_requests

List the requests in your Needs Approval inbox in the Schedule notifications panel. Access: read. REST: `GET /api/v1/quinyx/approval-requests`. MCP: `quinyx_read → list_approval_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `category` | string | no | One of absence_request, shift_booking, shift_swap, shift_unassignment_request, shift_assignment_away_unit. Default all. |
| `group_id` | string | no | Only requests of this unit or section. |

Returns request_id, category, employee, a one-line summary and when it was sent. These are the same five categories as the Needs Approval section of the panel. You see only the requests Quinyx sends to your account, so the list depends on your role and permissions. Pass a request_id to get_approval_request for the full request.

Example response:

```json
{
  "requests": [
    {
      "request_id": "77310",
      "category": "absence_request",
      "employee": "Elena Ruiz",
      "summary": "Absence 4 to 5 Nov 2026",
      "sent_at": "2026-10-21T16:40:00Z"
    },
    {
      "request_id": "77318",
      "category": "shift_swap",
      "employee": "Sam Okafor",
      "summary": "Swap Opening 28 Oct for Closing 29 Oct with Tom Becker",
      "sent_at": "2026-10-22T08:05:00Z"
    }
  ]
}
```

### get_approval_request

Read one request with the shifts it affects and what Quinyx warns about. Access: read. REST: `GET /api/v1/quinyx/requests/{request_id}/approval-request`. MCP: `quinyx_read → get_approval_request`.

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

Returns the period, the employee's comment and the shifts scheduled inside it. For an absence request it adds the holiday days left when the organization uses Time Trackers. For a shift booking or swap it lists the agreement rules the shift would break, the ones Quinyx marks with an exclamation mark.

Example response:

```json
{
  "request_id": "77310",
  "category": "absence_request",
  "employee": "Elena Ruiz",
  "period": {
    "from": "2026-11-04",
    "to": "2026-11-05"
  },
  "employee_comment": "Family visit.",
  "shifts": [
    {
      "shift_id": "90412",
      "shift_type": "Opening",
      "start": "2026-11-04T06:00",
      "end": "2026-11-04T14:00"
    },
    {
      "shift_id": "90437",
      "shift_type": "Opening",
      "start": "2026-11-05T06:00",
      "end": "2026-11-05T14:00"
    }
  ],
  "time_tracker": {
    "holiday_days_left": 11
  },
  "warnings": []
}
```

### list_timesheet_approvals

List punches of a unit in a date range with employee and manager attest status. Access: read. REST: `GET /api/v1/quinyx/groups/{group_id}/timesheet-approvals`. MCP: `quinyx_read → list_timesheet_approvals`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group_id` | string | yes | Unit or section id from list_groups. |
| `from` | string | yes | First day, YYYY-MM-DD. |
| `to` | string | yes | Last day, YYYY-MM-DD. |
| `employee_id` | string | no | Only this employee. |
| `status` | string | no | One of employee_missing_approval, manager_approval_missing, has_employee_approval, has_manager_approval. |

Returns one row per punch with the start and end, the original start and end, employee_attested, manager_attested and any warnings. The four status values match the attest filters of the Schedule view. Absences are included in the range with the same flags.

Example response:

```json
{
  "punches": [
    {
      "employee_id": "3011",
      "employee": "Tom Becker",
      "date": "2026-10-14",
      "start": "06:02",
      "end": "14:05",
      "original_start": "06:02",
      "original_end": "14:05",
      "employee_attested": true,
      "manager_attested": false,
      "warnings": []
    },
    {
      "employee_id": "3027",
      "employee": "Maria Silva",
      "date": "2026-10-15",
      "start": "06:00",
      "end": "14:00",
      "original_start": "06:00",
      "original_end": "13:48",
      "employee_attested": false,
      "manager_attested": false,
      "warnings": [
        "Automatic punch-out needs a time change before approval"
      ]
    }
  ]
}
```

### approve_request

Approve an absence request, shift booking, swap or unassignment request. Access: write, asks the user first. REST: `POST /api/v1/quinyx/requests/{request_id}/approve`. MCP: `quinyx_write → approve_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_id` | string | yes | Id from list_approval_requests. |
| `comment` | string | no | Comment for the employee and the audit log. |
| `shift_actions` | array | no | For absence requests, one object per shift: shift_id and action, one of unassign, delete, reassign, keep. Reassign also takes employee_id. |

Approving an absence request changes the schedule: each shift in the period is unassigned, deleted, reassigned or kept, as you set in shift_actions. The approved request leaves the Needs Approval list. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "77310",
  "category": "absence_request",
  "status": "approved",
  "employee": "Elena Ruiz",
  "shift_actions": [
    {
      "shift_id": "90412",
      "action": "unassign"
    },
    {
      "shift_id": "90437",
      "action": "unassign"
    }
  ],
  "comment": "Approved: 4 colleagues are scheduled each day. Both shifts are now open."
}
```

### deny_request

Deny an absence request, shift booking, swap or unassignment request. Access: write, asks the user first. REST: `POST /api/v1/quinyx/requests/{request_id}/deny`. MCP: `quinyx_write → deny_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_id` | string | yes | Id from list_approval_requests. |
| `comment` | string | no | The reason. Employees read it, so write it for them. |

Denies the request and removes it from Needs Approval; the schedule stays as it was. For swaps and unassignment requests, Quinyx shows your comment to the employee in the Qmail they receive and records it in the audit log. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "77325",
  "category": "absence_request",
  "status": "denied",
  "employee": "Sam Okafor",
  "comment": "Stocktake week, no absences possible 9 to 13 Nov."
}
```

### offer_shift

Offer an unassigned shift to one or more employees for their approval. Access: write, asks the user first. REST: `POST /api/v1/quinyx/shifts/{shift_id}/offer`. MCP: `quinyx_write → offer_shift`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `shift_id` | string | yes | Id of an unassigned shift from list_shifts. |
| `employee_ids` | array | yes | Employee ids from list_employees. |
| `comment` | string | no | Why you picked them. The employees see it in their Qmail. |

Works only on unassigned shifts in the published period and only if Offer shift is turned on in Account settings > Compliance settings. Each employee gets a Qmail. The first to accept is assigned the shift, and the others are told the offer is gone. If nobody accepts by the shift start, Quinyx denies the offer. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "offer_id": "5521",
  "shift_id": "90518",
  "status": "pending",
  "offered_to": [
    "Tom Becker",
    "Maria Silva",
    "Ana Lopez"
  ],
  "comment": "Open Friday opening shift after a sick call. First to accept gets it."
}
```

### add_absence

Add a full-length absence for an employee in a unit. Access: write, asks the user first. REST: `POST /api/v1/quinyx/employees/{employee_id}/absences`. MCP: `quinyx_write → add_absence`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `employee_id` | string | yes | Employee id from list_employees. |
| `group_id` | string | yes | Unit id from list_groups. |
| `start` | string | yes | Start, YYYY-MM-DD or YYYY-MM-DDTHH:MM. |
| `end` | string | yes | End, same format as start. |
| `absence_type` | string | yes | Name of an absence type your account has. |
| `all_day` | boolean | no | Treat the absence as whole days. Default false. |
| `approval` | string | no | Who must approve the absence: employee, manager or both. |
| `comment` | string | no | Optional comment. |

Does what the Add Absence panel does: it picks the employee, dates, absence type and who must approve, and saves. The response shows the employee's Time Tracker balance. Part-time absences, split per shift or per day, are not part of this tool. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "absence_id": "66104",
  "employee": "Maria Silva",
  "absence_type": "Sick leave",
  "start": "2026-10-26",
  "end": "2026-10-27",
  "all_day": true,
  "approval": "manager",
  "status": "saved"
}
```

### create_shift

Add a shift for an employee in a unit or section. Access: write, asks the user first. REST: `POST /api/v1/quinyx/employees/{employee_id}/shifts`. MCP: `quinyx_write → create_shift`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `employee_id` | string | yes | Employee id from list_employees. Passive employees are rejected. |
| `group_id` | string | yes | Unit or section id from list_groups. |
| `shift_type` | string | yes | Name of a shift type your account has. |
| `start` | string | yes | Start, YYYY-MM-DDTHH:MM. |
| `end` | string | yes | End, YYYY-MM-DDTHH:MM. |
| `comment` | string | no | Optional comment on the shift. |

Saves one shift like the Add shift panel. Quinyx scheduling warnings apply: an overridable warning is returned in the response, and a hard stop for a severe compliance breach fails the call with the rule that stopped it. The employee sees the shift once the period is published. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "shift_id": "90601",
  "employee": "Tom Becker",
  "shift_type": "Closing",
  "start": "2026-10-29T14:00",
  "end": "2026-10-29T22:00",
  "warnings": []
}
```

### attest_hours

Attest the punches and absences of one employee in a date range as manager. Access: write, asks the user first. REST: `POST /api/v1/quinyx/groups/{group_id}/hours/attest`. MCP: `quinyx_write → attest_hours`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group_id` | string | yes | Unit or section id from list_groups. |
| `employee_id` | string | yes | Employee id from list_employees. |
| `from` | string | yes | First day, YYYY-MM-DD. |
| `to` | string | yes | Last day, YYYY-MM-DD. |

Does what Attest all does in the Schedule view, for the range you pass, and returns how many punches and absences it attested. It follows your Time settings: with Hierarchical approval on, the employee must have approved first, and with Manager can approve employee off, the call fails. The attested hours can go into a payroll file. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "employee": "Tom Becker",
  "from": "2026-10-12",
  "to": "2026-10-18",
  "attested": {
    "punches": 5,
    "absences": 0
  },
  "manager_attested": true
}
```

### publish_schedule

Publish the schedule of a unit or section up to a date. Access: write, asks the user first. REST: `POST /api/v1/quinyx/groups/{group_id}/schedule/publish`. MCP: `quinyx_write → publish_schedule`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group_id` | string | yes | Unit or section id from list_groups. |
| `publish_until` | string | yes | Last day to publish, YYYY-MM-DD. An earlier date than the current one unpublishes the days after it. |

Publishes up to the unit's daybreak on that date and sends a Qmail to the employees who have an active role on the group, unless Pause notifications is on. Units with the Schedule approval flow send an approval request to the approver instead, and there the publish date cannot be reversed. A section can be published further out than its unit. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "group_id": "1042",
  "name": "Harbor Cafe",
  "published_until": "2026-11-12",
  "previous_published_until": "2026-11-05",
  "employees_notified": 14
}
```

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

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

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

2. **Sign in to Quinyx in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Quinyx 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 Quinyx 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 the absence requests waiting for me in Quinyx. Approve those where at least 3 colleagues are still scheduled each day and the shifts can stay open, deny the ones that overlap the stocktake week, and list the rest for me.
```

### Call Quinyx 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/quinyx 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/quinyx/shifts/90518/offer \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"employee_ids":["3011","3027","3044"],"comment":"Open Friday opening shift after a sick call. First to accept gets it."}'
```

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

```
{
  "offer_id": "5521",
  "shift_id": "90518",
  "status": "pending",
  "offered_to": [
    "Tom Becker",
    "Maria Silva",
    "Ana Lopez"
  ],
  "comment": "Open Friday opening shift after a sick call. First to accept gets it."
}
```

## Why use Cotlet for Quinyx?

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

## Is it safe to connect Quinyx to Cotlet?

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

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

## Is there a Quinyx MCP server on GitHub?

Quinyx publishes a REST API, so the realistic alternative is a script or integration built on it. It needs Integrations credentials from your account admin and a developer, and it cannot approve requests, offer shifts, attest hours or publish a schedule. Cotlet works in the web app your managers already use, hosted, and our team keeps it working.

|  | Quinyx API | Cotlet |
|---|---|---|
| Setup | Generate Version 3 credentials in Account Settings, pick scopes, request tokens, write and host the code | Sign up, sign in to Quinyx once, add one MCP server or API key |
| When Quinyx changes | You follow API version changes yourself; Quinyx points new work to v3 | Our team tests it daily and fixes it for you; failed calls are free |
| Your Quinyx session | A client ID and secret that sit in your own code or config | 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 | Tokens last 1 hour and your code has to renew them | Your Cloud Browser keeps you signed in; if Quinyx 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 | Wherever you host your integration | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Developer time to build and run it | 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 Quinyx 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 Quinyx API cost?

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

**Do I need to be technical?**

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

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

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

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

The role follows what you do by hand. Quinyx sends absence requests to managers with write access on the absence permission and a manager role above the employee, and shift bookings and swaps to managers with write access on the scheduling permission. Reaching Time and the time card needs at least read access on Transfer to payroll. A call without the permission fails with APP_PERMISSION_DENIED.

**Can the agent approve shift swaps from the mobile app?**

It works in the web app, which is where Quinyx wants swaps approved: the mobile Manager tab no longer supports shift swap approvals, and the help center sends managers to web.quinyx.com, Schedule > Notifications. Employees still request and accept swaps in the mobile app.

**Does my company sign in with SSO?**

Quinyx accepts a UserID of email, badge number or global login alias, then a password or your company's SSO provider. You sign in once in your Cloud Browser the way you do on web.quinyx.com. If your SSO asks for MFA, you complete it yourself in the Cloud Browser.

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

No. Every call to approve_request, deny_request, offer_shift, add_absence, create_shift, attest_hours or publish_schedule 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 Quinyx 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/quinyx 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.