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

Question Extend Plesk rest API with custom extension?

pascal20997

New Pleskian
Server operating system version
CentOS
Plesk version and microupdate number
Obsidian latest
Hi everyone,

I am developing a Plesk extension which analyses some data of our customers. This data should be transferred to another application using an API.

So as Plesk provides the v2 rest API with swagger files this is the way I want to use. The Plesk SDK gives some hint that there is a chance to extend the API using pm_Hook_ApiRest::getSchema() but I could not find any documentation how the Controller should be implemented to work with Plesk API routes.

Is anyone here who extended the Plesk API or at least tried to do?

Greetings,
Pascal
 
Back
Top