• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue REST API - Create Customer

gManNAtl

New Pleskian
I am working on an application to utilize the REST API and can't POST to the clients endpoint. I quit with my app and just went to the playground to test and it doesn't work there either. I simply get a 500 error either way. However, in the playground I can see a body message with error 1002 which seems to indicate the user already exists??

I have modified the playground JSON object as it doesn't seem like on a POST I should be passing in an id and guid value. The only required fields per the documentation are name, email, logon, and account type (although it seems password should be required as well). Even after modifying this in every variation I still get the 500 error. I even went into the PSA database to see if the dummy users I was testing with were created, but they were not there or in the gui.

All other endpoints work fine, and I can POST to domains for example with no problems, and all of the GETS work fine (or at least the ones I've tried).

Any help is greatly appreciated.
 
Hi,
I ran into this issue too. For me at least it turns out that the password complexity wasn't high enough when creating a new client. The API doesn't give helpful response. Pretty nasty bug. Hope this helps you!
 
Hello,
Thank you for drawing our attention to it! This improvement was reported as EXTREST-114.
Please try creating customer with more complex password.
 
Back
Top