API changelog

Uptrends API will be improved and extended over time. We’ll be adding new endpoints and methods for new functionalities.

When adding a new functionality, our goal is always to stay backward-compatible. However, sometimes change is inevitable and a new version of the API may not be compatible with what you’ve coded and used so far. You should check the API changelog regularly to stay on top of all changes and to act on those changes when necessary.

If you are looking for the documentation of the API, please check out the articles in the Uptrends API category.

Also, if you are interested in the changes to the Uptrends app, check out the general changelog.

July 2026

Manage OpenTelemetry export configurations using the new MonitorResultExportSettings API

A new set of MonitorResultExportSettings endpoints has been added to help you manage your Uptrends OpenTelemetry export configuration. The API lets you create, retrieve, update, and delete OpenTelemetry connections, rule sets, and export settings configured in Uptrends.

For more information, see the Uptrends API v4 MonitorResultExportSettings documentation.

Bearer authentication support in the Monitor and MonitorCheck APIs

The /Monitor and /MonitorCheck/{monitorCheckId}/MultiStepAPI endpoints now support configuring Bearer authentication for multi-step API monitors. When configured, the bearer token is automatically included in the request’s Authorization header. For security, the token value cannot be retrieved from any endpoint.

For more information, refer to the Uptrends API v4 Monitor and MonitorCheck documentation.

June 2026

Monitor API update: View who last updated a monitor

The /Monitor endpoint now returns the LastModifiedByOperatorId, which identifies the operator who last created or updated the monitor.

Manage custom integrations with new Integration/Custom endpoints

A new set of Integration/Custom endpoints has been added to retrieve, create, update, and delete custom integrations. For more information, see the Uptrends API v4 Integration documentation.

Manage API users with new ApiUser endpoints

A new set of ApiUser endpoints has been added to retrieve, create, update, and delete API users. For more information, see the Uptrends API v4 ApiUser documentation.

March 2026

Manage RUM websites efficiently with the API

RUM websites can now be fully managed through the API. The /RUM endpoint has been extended to support creating, updating, and deleting RUM website configurations, in addition to retrieving them. For more information, refer to the Uptrends API v4 RUM documentation.

September 2025

Introducing the MonitorCheck endpoint for Postman API monitors

The /MonitorCheck/{monitorCheckId}/PostmanAPI endpoint has been added to provide detailed monitoring information for individual Postman API monitor checks. This returns key results, such as HTTP status code, assertion outcomes, total execution time, response components, and other information for each API step.

For more information, refer to the Uptrends API v4 MonitorCheck documentation.

Monitor API update: Support for predefined variables in Postman API monitors

The /Monitor endpoint now also returns the PredefinedVariables field for Postman API monitors. This field contains all the user-defined and collection variables associated with the monitor.

"PredefinedVariables": [
    {
      "Key": "baseUrl",
      "Value": "{{prodEnvironment}}"
    },
    {
      "Key": "testEnvironment",
      "Value": "https://test-galactic.resorts.com/"
    },
    {
      "Key": "prodEnvironment",
      "Value": "https://https://prod-galactic.resorts.com/"
    },
    {
      "Key": "secretkey",
      "Value": "{{@VaultItem.70454a43-ef64-4f6a-aee0-3779654f1a31.Password}}"
    }
  ]

For more information, refer to the Postman API variables knowledge base article and the Uptrends API v4 Monitor documentation.

Monitor API update: Support for the latest Edge and Chrome user agents

The /Monitor endpoint now supports ChromeLatest and EdgeLatest as user agent values for the latest Chrome and Edge versions. You can also use these values with the /POST, /PUT, and /PATCH methods.

August 2025

Monitor API update: Deprecated fields

As of 27 August 2025, certain fields in the /Monitor endpoint were deprecated. To define error conditions and maintain compatibility with the Uptrends API, use the Monitor.ErrorConditions command.

May 2025

Upcoming breaking change: Deprecating API fields

As part of our ongoing efforts to optimize the Uptrends API, specific fields in the following Monitor endpoints will be deprecated, effective 27 August 2025:

• GET and POST /Monitor
• GET, PUT, and PATCH /Monitor/{monitorGuid}
• GET and POST /Monitor/MonitorGroup/{monitorGroupGuid}

The following deprecated fields will now be treated as Error condition types under the ErrorConditions array. Related fields will be merged into a single entry, replacing their previous usage as individual fields:

Below is an example of the updated API response. It is recommended that you adjust your API calls to use the ErrorConditions array. This aligns with the latest API structure and ensures correct API functionality.

{
  ...
  "ErrorConditions": [
    {
      "ErrorConditionType": "LoadTimeLimit1",
      "Value": "2500",
      "Effect": "Indicate"
    },
    {
      "ErrorConditionType": "LoadTimeLimit2",
      "Value": "5000",
      "Effect": "Error"
    },
    {
      "ErrorConditionType": "TotalMaxBytes",
      "Value": "5000000"
    },
    {
      "ErrorConditionType": "TotalMinBytes",
      "Value": "5000"
    },
    {
      "ErrorConditionType": "PageElementMaxSizeWithPercentage",
      "Value": "200000",
      "Percentage": "10"
    },
    {
      "ErrorConditionType": "PageElementFailedWithPercentage",
      "Percentage": "10"
    },
    { "ErrorConditionType": "HttpStatus",       
      "Value": "200"     
    }
  ],
 ...
}

Private Checkpoint Health Update

The GET /PrivateCheckpointHealth endpoint now returns the Warnings field, which contains all warning information associated with the server’s checkpoint. To know more, refer to the Uptrends API v4 Private location Checkpoint health documentation.

April 2025

Introducing the Private locations API​

A new set of API endpoints has been added to help you manage your Private locations configuration, including health and checkpoint information. To know more, refer to the Uptrends API v4 Private locations documentation.

March 2025

Monitor Group API Update

The /MonitorGroup endpoint now returns the number of credits used per monitor type:

• UsedBasicMonitorQuota — returns the number of credits used for Uptime or Basic monitors.
• UsedBrowserMonitorQuota — returns the number of credits used for Browser or Full-Page Check (FPC) monitors.
• UsedTransactionMonitorQuota — returns the number of credits used for Transaction monitors.
• UsedApiMonitorQuota — returns the number of credits used for Multi-step API (MSA) and Postman monitors.

Previously, the MonitorGroup API only returned the total number of credits available to the group for each monitor category. Now, it also returns the number of credits in use in the group for each monitor category.

February 2025

Cursor Parameter Value Update

The API Cursor parameter is a string value that works as a pointer to traverse data from the API response.

Cursors have now been updated to a longer string format to ensure safer data handling. All newly created cursors will now follow the new format, and the old formatted cursors will still continue to work until 1 April 2025. After that period, old cursors will no longer be available for use. It is recommended to generate new cursor values to keep them updated and working as expected.

Note that the Cursor parameter is available in the Monitor Check API and Alert API endpoints.

January 2025

Monitor API Update

The /Monitor endpoint now returns the LastModifiedDate, which contains the date and time the monitor was last updated. Previously, only the CreatedDate could be retrieved from the Monitor API.