---
title: Handling Updates to the REST API
slug: ps/help/en_us/vtm/restapi/handling-updates-to-the-rest-api
createdAt: 2026-08-02T09:26:02.635Z
---

## REST API Support in the Traffic Manager

The Traffic Manager typically supports several major versions of its REST API in any one release, and can additionally support several minor versions of each major version. The Traffic Manager employs this system to facilitate upgrading from an older supported version to a newer version with the least possible constraints on development time. Ivanti operates a policy of always warning about the impending removal of an API version in the release notes of the preceding Traffic Manager release.

The REST API version number is split into a major and minor component, and is two sets of digits separated by a dot. Using BNF notation, the follows rules apply:

```bash
<REST API version> ::= <major> "." <minor>
<major> ::= <non-negative integer>
<minor> ::= <non-negative integer>
```

Ivanti typically increments the version number in each release of the Traffic Manager, with the extent of the increment dependent on the changes introduced to the API since the preceding release. A significant API update necessitates incrementing the major component of the version number (with the minor version reset to 0). For example, from 3.4 to 4.0. A smaller API change increments only the minor component by 1, for example, from 3.4 to 3.5.

Major changes typically occur in the following situations:

- Removing or renaming a resource.
- Removing or renaming a property within a resource.
- Adding a property without a default to an existing resource.

Minor changes typically occur in the following situations:

- Adding a new resource to the API.
- Adding a new property with a default value to an existing JSON resource.

For more information, contact Technical Support.
