# Bug Report - PUT {{baseUrl}}/projects/:projectId "description" is not working as expected

**URL:** <https://community.awork.com/t/bug-report-put-baseurl-projects-projectid-description-is-not-working-as-expected/3660>\
**Category:** Developer Forum\
**Tags:** api\
**Created:** [20. Juni 2025 um 07:03 UTC](https://community.awork.com/t/bug-report-put-baseurl-projects-projectid-description-is-not-working-as-expected/3660 "2025-06-20T07:03:34Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sd1](https://avatars.discourse-cdn.com/v4/letter/s/7ea924/32.png) [@sd1](https://community.awork.com/u/sd1)\
**Post date:** [20. Juni 2025 um 07:03 UTC](https://community.awork.com/t/bug-report-put-baseurl-projects-projectid-description-is-not-working-as-expected/3660/1 "2025-06-20T07:03:34Z")

</div>

**Steps to reproduce**

1. Create a project in awork
2. Add a Description
3. Update the awork Project via the API (PUT), e.g. with a new name

See:

> **[Updates the project with the specified id. | awork API | Documentation](https://developers.awork.com/apiv1/projects/updates-the-project-with-the-specified-id)**

**Unter Request**  
This endpoint expects an object.  
description \> string or null \> Optional

and Loom: [Fehler beim Aktualisieren eines Projekts über die API 🐛 | Loom](https://www.loom.com/share/9d0110daa9e14e99969eab2fa0585c44?sid=66eb3e31-ca69-4c5a-a064-4b00861375b1)

**Actual result**

1. If no „description“ attribute is provided, the API sets the Project description to „null“ (String)
2. If „description“ attribute is provided as null, the API sets the Project description to „null“ (String)

**Expected result**

1. If no „description“ attribute is sent, the awork project description remains as it is.

---

<div class="post-metadata">

**Author:** ![Nils](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/nils/32/96_2.png) [@Nils](https://community.awork.com/u/Nils)\
**Post date:** [20. Juni 2025 um 07:11 UTC](https://community.awork.com/t/bug-report-put-baseurl-projects-projectid-description-is-not-working-as-expected/3660/2 "2025-06-20T07:11:45Z")

</div>

Hi @sd1 ,

we only have put endpoints. And put endpoints require by specification to sent the whole object and not just a subset of properties. So if you leave those properties out we set them to null or the default value of the property.

> **[Difference Between PUT and PATCH Request - GeeksforGeeks](https://www.geeksforgeeks.org/javascript/difference-between-put-and-patch-request/)**
>
> Your All-in-One Learning Portal: GeeksforGeeks is a comprehensive educational platform that empowers learners across domains-spanning computer science and programming, school education, upskilling, commerce, software tools, competitive exams, and...

I hope that helps.

Best

Nils

---

<div class="post-metadata">

**Author:** ![sd1](https://avatars.discourse-cdn.com/v4/letter/s/7ea924/32.png) [@sd1](https://community.awork.com/u/sd1)\
**Post date:** [20. Juni 2025 um 07:53 UTC](https://community.awork.com/t/bug-report-put-baseurl-projects-projectid-description-is-not-working-as-expected/3660/3 "2025-06-20T07:53:54Z")

</div>

Hey @Nils dann habt ihr wohl einen PUTCH Endpoint, die anderen Werte werden ja auch nicht überschrieben;)

Gibt es ein PATCH endpoint oder müssen wir vor dem Update die Daten erst mit GET abrufen?

---

<div class="post-metadata">

**Author:** ![Nils](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/nils/32/96_2.png) [@Nils](https://community.awork.com/u/Nils)\
**Post date:** [20. Juni 2025 um 08:02 UTC](https://community.awork.com/t/bug-report-put-baseurl-projects-projectid-description-is-not-working-as-expected/3660/4 "2025-06-20T08:02:16Z")

</div>

Das kann eigentlich nicht sein. Welcher Wert wird nicht überschrieben? Kannst du mir zufällig die Trace-Id aus dem Responds header geben?

---

<div class="post-metadata">

**Author:** ![sd1](https://avatars.discourse-cdn.com/v4/letter/s/7ea924/32.png) [@sd1](https://community.awork.com/u/sd1)\
**Post date:** [20. Juni 2025 um 09:38 UTC](https://community.awork.com/t/bug-report-put-baseurl-projects-projectid-description-is-not-working-as-expected/3660/5 "2025-06-20T09:38:56Z")

</div>

Klar, gerne:

trace-id  
ef2e3779773080529fe6d0edb07966bf

Nur um komplett zu sein: Eure Documentation beschreibt einen PATCH endpoint, anders kann ich „Optional“ nicht lesen. Ich denke dass ist auch das, was euere Kunden brauchen. Alternativ muss ich vor jedem PUT ein GET machen…

---

<div class="post-metadata">

**Author:** ![Nils](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/nils/32/96_2.png) [@Nils](https://community.awork.com/u/Nils)\
**Post date:** [20. Juni 2025 um 09:52 UTC](https://community.awork.com/t/bug-report-put-baseurl-projects-projectid-description-is-not-working-as-expected/3660/6 "2025-06-20T09:52:49Z")

</div>

Sehe ich etwas anders. 😉 Es ist optional, weil du es auf null setzen kannst und das Feld nicht ein Pflichtfeld ist. Ich habe gerade geschaut in dem trace werden alle Felder auf null gesetzt und der Name auf den gesendeten wert.

Genau - man muss vor jedem PUT ein GET machen. Das gilt aktuell für alle unsere Endpoints.

Viele Grüße

Nils