Devolutions Server REST API - Create entries in shared vault - error 500

Devolutions Server REST API - Create entries in shared vault - error 500

avatar

Hello,

i have tried using the API of the devolutions server (newest version 2025.1.5.0).
We are using a shared vault on MSSQL. I can login, GET the vaults and then GET entries inside that vault but as soon as i want to create entries using POST to /api/v1/vault/{vaultId}/entry, i get error 500 (entires i tried to create were folders and sshconnections). i have tried with different JSONs but i only get this error: "the specified entry type is not supporting on edit"


I can not find any information about this error or if i try doing something that is not allowed/supported - any help? :)


Best Regards
Michael

grafik.png

All Comments (5)

avatar

Hello,

What entry type are trying to create?

The DVLS REST API only allows the creation of credential entries.

If it is this entry type you want to create and get the error, could you share the JSON you use? Make sure you hide sensitive information in your post.

Best regards,

Érica Poirier

avatar

Thanks!

as i mentioned in my initial post i tried to create ssh connection entries and folders as well as some other connections but not credentials! Is there anywhere this is documented? since i could not figure it out myself.
Also, what is the reason for this? Automating the creation of those/all entries was a reason we switched from rdm with sql-datasource to devolutions server.

Best Regards
Michael

avatar

Hello,

Thank you for your feedback. I'm sorry that I missed the entry type you are trying to create.

The v1 of the REST API is mainly for DevOps operations to manage credential entries.

The Devolutions PowerShell module makes it easy to create any entry type. Our GitHub repository contains a few script samples.

Let us know if you need assistance with the Devolutions PowerShell module.

Best regards,

Érica Poirier

avatar

Hello,

thanks for clarifying! i am kind of sad that this is not possible via the REST API since i imagined this is exactly what the REST API is for and i dont want to use powershell but i will look into it.
Are there plans to expand the API feature at all?

Best Regards

Michael

avatar

Hello Michael,

Thank you for this feedback.

All the ideas are always welcomed.
I recommend posting those in our feature request thread.

Best regards,

Patrick Ouimet