---
title: "Updates documentation"
method: PUT
path: "/documentations/{documentationId}"
tags: ["Documentations"]
---

# Updates documentation

`PUT /documentations/{documentationId}`

## Path parameters

- `documentationId` integer, required

## Request body

- UpdateDocumentationRequest
  - `assignment_id` integer — The appointment id to add to the documentation
  - `author_id` integer — The author of this documentation (only customizable for type TIME)
  - `title` string — The documentation title
  - `description` string — The documentation description
  - `type` 'NOTE' | 'DRAFT' | 'PHOTO' | 'SIGNING' | 'TIME' | 'PDF' | 'ATTACHMENT' | 'MATERIAL' — The documentation type
  - `state` 'ACCEPTED_WITH_COMMENT' | 'ACCEPTED_WO_COMMENT', nullable — Documentation state
  - `state_text` string — Documentation Signing text (Like 'Vertragsgerechet und mangelfrei...' to display and store
  - `working_time` integer — The working time in minutes
  - `driving_time` integer — The driving time in minutes
  - `break_time` integer — The break time in minutes
  - `documented_on` string, date-time — The datetime, when the documentation has been documented has been created
  - `upload` string, binary — First documentation upload file. PLEASE ADD _method=put parameter and change method to POST, if you send file uploads (PHP issue. More info: https://stackoverflow.com/questions/39942670/how-to-send-put-request-with-a-file-and-an-array-of-data-in-laravel)
  - `upload2` string, binary — Second documentation upload file. PLEASE ADD _method=put parameter and change method to POST, if you send file uploads (PHP issue. More info: https://stackoverflow.com/questions/39942670/how-to-send-put-request-with-a-file-and-an-array-of-data-in-laravel)
  - `source` string — The document source
  - `source_external_id` string — The document source_external_id

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