This article applies as of PRTG 26.4.126

The new UI and API v2

With PRTG 21.4.73, Paessler introduced the first version of the new UI and API v2 to make available for you a state-of-the-art web interface and RESTful API. 

As of PRTG 25.2.106, new PRTG installations have the new UI and API v2 activated by default. 

In existing installations, the new UI and API v2 are activated automatically when you update to PRTG 26.4.126.


This article lists the available features, known limitations, the FAQ, and the link to the roadmap with our plans for the new UI and API v2.


System requirements

The new UI and API v2 run as an additional service, the PRTG Application Server, which has its own resource footprint. If the installation follows the system requirements for PRTG, no extra precautions are necessary. If the installation already runs considerably outside these recommendations, activate the new UI and API v2 with caution.

Before PRTG activates the new UI and API v2 automatically during an update, it checks whether enough memory is free. If not, PRTG does not activate the new UI and API v2. If you want to activate the new UI and API v2 manually later on, see PRTG Manual: New User Interface.


Ports

  • The new UI and API v2 use port 1616 for secured connections.
  • The new UI and API v2 use port 1615 for unsecured connections.


Limitations

  • Not all features that are available in the classic UI are also available in the new UI.
  • Not all features that are available in the new UI are also available in the API v2. For the complete list of endpoints, see the PRTG API v2 Reference.


Unavailable features

Some of the features that are not available in both the new UI and API v2:

  • PRTG failover cluster. If a PRTG installation runs in cluster mode, the Open new UI button does not appear.
  • Device templates with shared notifications and auto-discovery schedules.
  • Filtered sensor views (libraries and lists).
  • Top lists for Packet and Flow sensors.
  • Messages view for syslog and SNMP traps.


Swagger

To open Swagger, go to http(s)://<yourprtgserver>:<port>/api/v2/oas/.


Deactivation

If you want to deactivate the new UI and API v2, see PRTG Manual: New User Interface.


Frequently asked questions (FAQ)

What is the PRTG new UI and API v2?

The new UI is the redesign of the classic PRTG web interface, based on user research. The new UI is fully responsive and works on every screen size. Paessler follows the Web Content Accessibility Guidelines (WCAG) to make PRTG accessible to as many people as possible.

The PRTG API v2 is the new RESTful API of PRTG. The goal of the API v2 is to help you automate monitoring and integrate it with other tools. The API v2 is fully documented and consistent across all endpoints.


Does Paessler plan to deactivate the classic PRTG web interface and API (v1) soon?

Paessler plans to deactivate the classic PRTG web interface and API (v1) once the new UI and API v2 are stable and feature-complete. Paessler will communicate the deactivation period with advance notice.


What does it mean that the new UI and API v2 are activated in my installation?

When the new UI and API v2 are active, PRTG runs an additional service called the PRTG Application Server.

With the new UI and API v2 active, the classic PRTG web interface, the new UI, the PRTG API (v1), and the PRTG API v2 are all available side by side. Depending on the network and firewall rules, users can access them via different ports.


What is the PRTG Application Server?

The PRTG Application Server is the service that delivers the new UI and API v2. Furthermore, after PRTG installs the Application Server, it automatically creates the Application Server Health (Autonomous) sensor, which monitors the status of the PRTG Application Server.


Does the PRTG Application Server support the same connection security settings as the PRTG web server?

The PRTG Application Server uses TLS 1.2 and TLS 1.3 for the connection to the PRTG core server.

Note: If a registry key overrides the TLS version and cipher suites of PRTG web server connections, these settings do not apply to the PRTG Application Server.


Does the PRTG Application Server support custom SSL certificates?

Yes, the PRTG Application Server uses the same certificate as the PRTG web server. To use a custom SSL certificate, move the certificate file to the \cert subfolder in the PRTG program directory. For more information, see How to use your own SSL certificate with the PRTG web server.



More