---
title: "Updates specific timesheet activity"
method: PUT
path: "/timesheets/activities/{activityId}"
tags: ["Timesheet activities"]
---

# Updates specific timesheet activity

`PUT /timesheets/activities/{activityId}`

## Path parameters

- `activityId` integer, required

## Request body

- UpdateTimesheetActivityRequest
  - `type_id` integer — Timesheet activity type (activity activity)
  - `timesheet_id` integer — Timesheet on which the activity (activity) should be recorded on
  - `assignment_id` integer — Optional: The appointment id on which the timesheet activity should be booked on.
  - `start` string, date-time — Timesheet activity start date
  - `end` string, date-time, nullable — Timesheet activity end date
  - `adjust_blocking` boolean — Sometimes activities before or after would block this new activity. Set this parameter to true, to shorten or delete the blocking activities.
  - `start_lat` number, float, nullable — GPS latitude captured at activity start
  - `start_lng` number, float, nullable — GPS longitude captured at activity start
  - `end_lat` number, float, nullable — GPS latitude captured at activity end
  - `end_lng` number, float, nullable — GPS longitude captured at activity end

## Response `200`

The request was successful.

## Other responses

- `401` — The request lacks valid authentication credentials.
- `403` — The token is valid but lacks the permission for this action.
- `404` — The requested resource could not be found.
- `422` — The request was well-formed but contains semantic errors (validation failed).
- `500` — An unexpected error occurred on the server (e.g. a requested relation does not exist).

---

[API](https://skmtc.net/craftboxx/apis/craftboxx-api-documentation.md) · [All operations](https://skmtc.net/craftboxx/apis/craftboxx-api-documentation/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/craftboxx/craftboxx-api-documentation/versions/c01f07a02f77/schema)