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

> Approve one employee's submitted timesheet for a pay period. Your account needs approve permission. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/connecteam/approve_timesheet

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 one employee's submitted timesheet for a pay period. Your account needs approve permission.

Connecteam API: https://cotlet.dev/docs/api/connecteam.md

`POST https://cotlet.dev/api/v1/connecteam/time-clocks/{time_clock_id}/timesheet/approve`

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

Approves the timesheet like the Approve button in the upper right of the employee's timesheet. It works only on a time clock with Timesheets approval on, for a pay period, and with an admin account that may approve; otherwise it fails with APP_PERMISSION_DENIED. Once approved, only an admin with reopen permission can change the timesheet, and Connecteam notifies the employee right away. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `time_clock_id` | integer | yes | Time clock ID from list_time_clocks. |
| `user_id` | integer | yes | User ID from list_users or list_timesheets. |
| `period_start` | date | yes | First day of the pay period, YYYY-MM-DD. |
| `period_end` | date | yes | Last day of the pay period, YYYY-MM-DD. |

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/connecteam/time-clocks/2041/timesheet/approve \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"user_id":8821034,"period_start":"2026-10-12","period_end":"2026-10-18"}'
```

**Python**

```python
result = client.call("connecteam", "approve_timesheet", {"time_clock_id":2041,"user_id":8821034,"period_start":"2026-10-12","period_end":"2026-10-18"})
```

**Node.js**

```js
const result = await cotlet.call('connecteam', 'approve_timesheet', {"time_clock_id":2041,"user_id":8821034,"period_start":"2026-10-12","period_end":"2026-10-18"});
```

**CLI**

```bash
cotlet call connecteam approve_timesheet --data '{"time_clock_id":2041,"user_id":8821034,"period_start":"2026-10-12","period_end":"2026-10-18"}'
```

## Example response

```json
{
  "approved": true,
  "time_clock_id": 2041,
  "user_id": 8821034,
  "name": "Dana Whitfield",
  "period_start": "2026-10-12",
  "period_end": "2026-10-18",
  "total_hours": 38.5
}
```

Previous: [List tasks](https://cotlet.dev/docs/api/connecteam/list_tasks.md)
Next: [Copy the previous week](https://cotlet.dev/docs/api/connecteam/copy_previous_week.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.