REST services

Our philosophy about REST services

Universal Messenger provides only a few REST endpoints out of the box, because we have made the experience that generic endpoints are not what you really need in the project.

Instead, we make it as easy as possible for the developer to implement their own application specific endpoints. By doing this, we achieve much better runtime efficiency, as the number of REST calls can be kept to a minimum by using optimally matched endpoints. (Fewer discrete / sequential REST calls => more efficient, faster and more reliable processing at runtime).

The developer has the choice of strictly following the REST pattern or preferring to implement custom RPC (Remote Procedure Calls).

A detailled documentation of the REST services provided out of the box can be found under Help / REST services or online under https://downloads.universal-messenger.de/knowledge-base/documentation/universal-messenger/html/restapidoc/index.html.

Implementing REST endpoints

There are three different approaches to implementing a REST endpoint:

• Functional REST endpoints (the new and preferred way to go)

• Class based REST endpoints

• Classic REST controllers