What’s new

#HTTPS monitors now support additional TLS and HTTP versions

HTTPS monitors now support TLS 1.3, HTTP/2, and HTTP/3 versions, enhancing security and performance for monitored endpoints.

When you select any of these options, only checkpoints that are capable of supporting these versions will be available for use. Alternatively, you can select Negotiate to enable the client and server to automatically negotiate for the HTTP version to use, preferring HTTP/2 over HTTP/1.1.

While support for HTTP/3 is available, it is not currently recommended for use due to compatibility and stability limitations.

Read more

#Postman API monitors now auto-retrieve and display collection variables

When you import a Postman collection that uses variables like {{VariableName}} in requests, scripts, or environments, the Postman API monitor now automatically detects and displays these variables as pre-defined monitor variables. You can easily populate their values either through plain text or using the Vault. This is helpful when authenticating with APIs that require a username, password, or secret key.

This behavior also works similarly to Multi-step API variables.

Read more

#New transaction monitor setup options: Build your own or start with an example

Similar to creating a Multi-step API monitor, you can now also create transaction monitors using a ready-made, fully functional example that you can easily customize and test right away. This example allows you to test a transaction flow when booking and submitting an order on a fictional website, http://galacticresorts.com/Products. Additionally, you still have the flexibility to build your own monitor from scratch, depending on your monitoring needs.

Read more