HTTP PATCH Method is not updating attributes
Hello,
We are using Remote Desktop Manager v2025.2.14.0.
I am working with some automations that leverage the API, and it appears as though the PATCH method does not work, despite receiving a HTTP 200 response back from the server.
Specifically, I am trying to change some attributes on an existing entry in our vault. I am sending a PATCH to this endpoint:
https://our-remote-desktop-manager.com/dps/api/v1/vault/{{vaultId}}/entry/{{entryId}}
And, I'm sending the following raw payload with the PATCH request:
{"name":"Test Device Name", "description" : "Test Description via API call"}
I receive an HTTP 200 back from RDM.. but when I go and check the vault, nothing has changed. If I look at the History section of the device entry in the RDM web interface, I do see the change event in the history.
Do you have any idea what the issue could be?
All Comments (2)
Hi,
Thanks for the details.
Quick admin note first, I moved this thread under our DVLS category so it lands in the right queue, since the endpoint you're hitting (/dps/api/v1/...) is served by Devolutions Server rather than the RDM client itself.
Before we dig into the PATCH behavior, you're on 2025.2.14.0 and I'd like you to update to the current extended maintenance build for the 2025.2 line first, then re-run the exact same call.
That channel carries rolled-up fixes for 2025.2 without moving you to a new feature release, and if this is something we've already addressed on the server side it will simply go away after the update.
You can grab the extended maintenance build and its release notes from your Devolutions customer portal.
Please retest once you're on that build and let me know whether the PATCH still returns 200 with a History entry but no persisted change. If it does, we'll go deeper from there.
Best regards,
Patrick Ouimet
Thank you, Patrick. We'll try to update and test again soon.