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

# Approve a request

> Approve an absence request, shift booking, swap or unassignment request. Inputs, cURL, Python and Node.js examples and an example response.

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

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)

Approve an absence request, shift booking, swap or unassignment request.

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

`POST https://cotlet.dev/api/v1/quinyx/requests/{request_id}/approve`

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

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.

## Parameters

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

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/quinyx/requests/77310/approve \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"comment":"Approved: 4 colleagues are scheduled each day. Both shifts are now open.","shift_actions":[{"shift_id":"90412","action":"unassign"},{"shift_id":"90437","action":"unassign"}]}'
```

**Python**

```python
result = client.call("quinyx", "approve_request", {"request_id":"77310","comment":"Approved: 4 colleagues are scheduled each day. Both shifts are now open.","shift_actions":[{"shift_id":"90412","action":"unassign"},{"shift_id":"90437","action":"unassign"}]})
```

**Node.js**

```js
const result = await cotlet.call('quinyx', 'approve_request', {"request_id":"77310","comment":"Approved: 4 colleagues are scheduled each day. Both shifts are now open.","shift_actions":[{"shift_id":"90412","action":"unassign"},{"shift_id":"90437","action":"unassign"}]});
```

**CLI**

```bash
cotlet call quinyx approve_request --data '{"request_id":"77310","comment":"Approved: 4 colleagues are scheduled each day. Both shifts are now open.","shift_actions":[{"shift_id":"90412","action":"unassign"},{"shift_id":"90437","action":"unassign"}]}'
```

## 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."
}
```

Previous: [List punches and their attest status](https://cotlet.dev/docs/api/quinyx/list_timesheet_approvals.md)
Next: [Deny a request](https://cotlet.dev/docs/api/quinyx/deny_request.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.