• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue REST API - Create Customer

G

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.
 
You must log in or register to reply here.

Similar threads

K
Question How to restrict customer access the REST API?
Replies
2
Views
854
Kaspar
K
R
Resolved How to activate DNSSEC automatically via Plesk API (REST or XML)?
Replies
2
Views
3K
Riculum
R
W
Resolved Rest api breaking change with 18.0.18 #4 ??
Replies
10
Views
3K
Sofiia Kulish
Sofiia Kulish
burnley
Question granular scope permissions for Plesk REST API
Replies
2
Views
902
burnley
burnley
T
Input [Feature Request] Add php_handler_id to Plesk Rest API [GET] /domains
Replies
4
Views
5K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top