All Classes Files Functions Variables Enumerations Enumerator Groups Pages
About Kerio API
With the Kerio Connect Administration API, you can programmatically access your Kerio Connect server, integrate it with third-party solutions or write simple scripts to handle advanced administration tasks.
You just connect over HTTPS, send a request in a well-known human-readable format (JSON) and receive a response in the same format.

Scope

The administration API provides all actions that are available in the Connect administration (our Connect web administration uses the same Connect Administration API).
As an example, you can list Users, add new User, edit Resources, read Logs, setup Spam Rules – but the API is much more complex.

Out of Scope

Following features are not part of this API:
  • Message Store API. Work with emails, contacts, calendars, tasks, notes. Various actions and hooks when delivering/sending emails. For instance, you can not send an email directly.
  • WebMail API or customization. For example, you can not access calendars or customize WebMail skins.
  • Settings or configuration which is not available in the web administration. The only way is to set the appropriate configuration file.

Licensing

Kerio API is a part of the Kerio products and is governed by the product’s license. In short, you need a license to run Kerio Connect and the license also entitles you to use the API on your server.
Third-party independent software vendors may distribute their applications both for free or for profit. There is no royalty fee for the API. We only kindly ask you to let us know at connect-api@kerio.com about your applications.

Disclaimer

User acknowledges that Kerio provides no warranties with this API and makes no guarantees that it will operate continuously or for any specific purpose. Moreover, User agrees that Kerio cannot be held responsible for any defects in the API or for any negative or damaging impact on User’s operating environment as a result of the use thereof. If User experiences problems with the API, User acknowledges that Kerio is not obligated to correct such problems. Finally, User understands that Kerio may alter/update the API at any time and has no obligation to announce such changes.