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

# Create a shift

> Add a shift for an employee in a unit or section. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/quinyx/create_shift

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Add a shift for an employee in a unit or section.

Quinyx API: https://cotlet.dev/docs/api/quinyx.md

`POST https://cotlet.dev/api/v1/quinyx/employees/{employee_id}/shifts`

Access: write. Confirm: waits for the user's OK before it runs.

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.

## Parameters

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

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/quinyx/employees/employee_8c41d2/shifts \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"group_id":"group_8c41d2","shift_type":"shift type","start":"start","end":"end"}'
```

**Python**

```python
result = client.call("quinyx", "create_shift", {"employee_id":"employee_8c41d2","group_id":"group_8c41d2","shift_type":"shift type","start":"start","end":"end"})
```

**Node.js**

```js
const result = await cotlet.call('quinyx', 'create_shift', {"employee_id":"employee_8c41d2","group_id":"group_8c41d2","shift_type":"shift type","start":"start","end":"end"});
```

**CLI**

```bash
cotlet call quinyx create_shift --data '{"employee_id":"employee_8c41d2","group_id":"group_8c41d2","shift_type":"shift type","start":"start","end":"end"}'
```

## Example response

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

Previous: [Add an absence](https://cotlet.dev/docs/api/quinyx/add_absence.md)
Next: [Attest worked hours](https://cotlet.dev/docs/api/quinyx/attest_hours.md)

---

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.