• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Forwarded to devs [REST API] owner_login not sown on /clients methode

Kaspar

API expert
Plesk Guru
Username:

TITLE

[REST API] owner_login not sown on /clients methode

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk 18.0.46, CentOS 7.9

PROBLEM DESCRIPTION

In the Swagger Scheme of the API (and also in the example provided on API the playground) the owner_login is mentioned in the response of the /client and /client/{id} methodes. However owner_login is never shown in any API response.

Example provided on the API playground
OWHE1xj.png


Actual response from API
Kl6O3Bt.png


This makes me wonder if this is a bug? Should owner_login be shown in the respons? Or is this correct behavior and is the documentation incorrect, accidently mentioning owner_login when it shouldn't?

STEPS TO REPRODUCE

1) Add a customer to Plesk
2) Run the /client methode from the API

ACTUAL RESULT

owner_login is not shown in response

EXPECTED RESULT

Expected owner_login to be shown as mentioned in the Swagger Scheme

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Answer the question
 
Thank you.
The bug EXTREST-124 has been confirmed and submitted.
 
Back
Top