Generell PSU API Problems (2026.3.3)

Generell PSU API Problems (2026.3.3)

avatar
Dynamic66

https://docs.devolutions.net/powershell-universal/api/endpoints

  1. The log is not live and is lacking a refresh button. Currently only refreshing the page shows new logs.

  2. The documentation states: "You can write to the live log from within your endpoints with cmdlets like Write-Host."However, that does not work. Only Write-PSUError seems to write anything.

  3. I would appreciate it if the documentation contained more examples on how to use the Test tab correctly.

  4. Looking into the dev tools shows requests to /assets 404 Not Found. This is for all admin UI pages as far as i can tell

Please refer to my other issues for questions about my setup.

1

All Comments (4)

avatar
rubentapia

Hello Dynamic66,

Thank you for reporting these items.

We will start by reviewing these four points against PSU 2026.3.3, with particular focus on the Live Log behavior, the documented Write-Host behavior, the Test tab, and the /assets 404 requests in the Admin UI.

At this point, I do not need any additional information from you. I will update the thread once we have completed the initial review.

Best regards,

Ruben Tapia

1
avatar
Dynamic66

Found another API issue.

I have an API that has always used POST, with me never changing the method. Today, I fixed a typo in the request path, and after that, the API method automatically changed to GET. I changed it back to POST and confirmed that my API works again successfully. After a few minutes, I get a 404 when using the API, and I see that the method has been reset to GET again. I don't know what behavior could have triggered the reset the second time. Maybe updating the API script again, but I have never had that problem before when making modifications.

avatar
rubentapia

Hello @Dynamic66

Thank you for the additional information.

This is very useful. We will adjust the lab to focus specifically on the HTTP method behavior, especially whether a POST endpoint can unexpectedly revert to GET after changes to the endpoint configuration or script.

We will include this scenario in the next round of testing and update the thread with the results.

Best regards,

Ruben Tapia

avatar
rubentapia

Hello @Dynamic66

Thank you again for the additional details.

We completed a focused test on PSU 2026.3.3 around the HTTP method behavior you reported.

In our lab, we created a POST endpoint and then tested both scenarios separately:

- Editing only the endpoint URL

- Editing only the endpoint script

In both cases, the endpoint remained configured as POST in the Admin UI, in the persisted endpoints.ps1 configuration, and when tested with external HTTP requests. We were not able to reproduce an automatic POST to GET change.

One useful finding is that newly created endpoints default to GET, but editing an existing POST endpoint did not reset the method in our testing.

The next highest-value check would be on your environment if this happens again. If possible, please compare the method shown in the UI with the corresponding sanitized endpoint definition in endpoints.ps1 immediately after the change occurs, and let us know what action was performed just before it changed.

Best regards,

Ruben Tapia

1