• 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.

Standards in XML API

P

Patrick M

Guest
I am a new user of the Plesk API and I was struck by the problematic schema validations.

One rather curious validation exception I got was because I reused the same code to generate the inner elements of a Client/add and a Client/set xml requests.

When revising the schema, I understood that the exception was thrown because the sequence order was not respected:

ADD: <hosting> comes before <limits>
SET: <hosting> comes after <limits>

Working around this situation involves making two specific routines for the two calls, not very pleasant when doing maintenance.

Any ideas regarding this ?
 
You must log in or register to reply here.

Similar threads

R
Question How do I list Web Users with the XML API in Plesk Obsidian?
Replies
2
Views
1K
Reinier Post
R
Giu
Issue API Error after 18.0.59 Update 2
Replies
1
Views
588
Kaspar
K
P
Question XML-API add db_user
Replies
1
Views
788
Kaspar
K
S
Resolved XML API Proxmox Acme Plugin Failure
Replies
1
Views
2K
seek1338
S
P
Resolved Problems with an Excel VBA script using XML API
Replies
3
Views
2K
Peter_S
P
Back
Top