Update deprecated API versions

Author: dominicbetts

articles/iot-central/core/howto-authorize-rest-api.md

@@ -86,7 +86,7 @@ Using the REST API:
 1. Use the REST API to retrieve a list of role IDs from your application:
 
     ```http
-    GET https://{your app subdomain}.azureiotcentral.com/api/roles?api-version=2022-05-31
+    GET https://{your app subdomain}.azureiotcentral.com/api/roles?api-version=2022-07-31
     ```
 
     The response to this request looks like the following example:
@@ -113,7 +113,7 @@ Using the REST API:
 1. Use the REST API to create an API token for a role. For example, to create an API token called `operator-token` for the operator role:
 
     ```http
-    PUT https://{your app subdomain}.azureiotcentral.com/api/apiToken/operator-token?api-version=2022-05-31
+    PUT https://{your app subdomain}.azureiotcentral.com/api/apiToken/operator-token?api-version=2022-07-31
     ```
 
     Request body:

articles/iot-central/core/howto-control-devices-with-rest-api.md

@@ -52,7 +52,7 @@ In IoT Central, a module refers to an IoT Edge module running on a connected IoT
 Use the following request to retrieve the components from a device called `temperature-controller-01`:
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/devices/temperature-controller-01/components?api-version=2022-05-31
+GET https://{your app subdomain}.azureiotcentral.com/api/devices/temperature-controller-01/components?api-version=2022-07-31
 ```
 
 The response to this request looks like the following example. The `value` array contains details of each device component:
@@ -87,7 +87,7 @@ The response to this request looks like the following example. The `value` array
 Use the following request to retrieve a list of modules running on a connected IoT Edge device called `environmental-sensor-01`:
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/devices/environmental-sensor-01/modules?api-version=2022-05-31
+GET https://{your app subdomain}.azureiotcentral.com/api/devices/environmental-sensor-01/modules?api-version=2022-07-31
 ```
 
 The response to this request looks like the following example. The array of modules only includes custom modules running on the IoT Edge device, not the built-in `$edgeAgent` and `$edgeHub` modules:
@@ -110,15 +110,15 @@ The response to this request looks like the following example. The array of modu
 Use the following request to retrieve a list of the components in a module called `SimulatedTemperatureSensor`:
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/devices/environmental-sensor-01/modules?api-version=2022-05-31
+GET https://{your app subdomain}.azureiotcentral.com/api/devices/environmental-sensor-01/modules?api-version=2022-07-31
 ```
 
 ## Read telemetry
 
 Use the following request to retrieve the last known telemetry value from a device that doesn't use components. In this example, the device is called `thermostat-01` and the telemetry is called `temperature`:
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/devices/thermostat-01/telemetry/temperature?api-version=2022-05-31
+GET https://{your app subdomain}.azureiotcentral.com/api/devices/thermostat-01/telemetry/temperature?api-version=2022-07-31
 ```
 
 The response to this request looks like the following example:
@@ -133,7 +133,7 @@ The response to this request looks like the following example:
 Use the following request to retrieve the last known telemetry value from a device that does use components. In this example, the device is called `temperature-controller-01`, the component is called `thermostat2`, and the telemetry is called `temperature`:
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/devices/temperature-controller-01/components/thermostat2/telemetry/temperature?api-version=2022-05-31
+GET https://{your app subdomain}.azureiotcentral.com/api/devices/temperature-controller-01/components/thermostat2/telemetry/temperature?api-version=2022-07-31
 ```
 
 The response to this request looks like the following example:
@@ -148,7 +148,7 @@ The response to this request looks like the following example:
 If the device is an IoT Edge device, use the following request to retrieve the last known telemetry value from a module. This example uses a device called `environmental-sensor-01` with a module called `SimulatedTemperatureSensor` and telemetry called `ambient`. The `ambient` telemetry type has temperature and humidity values:
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/devices/environmental-sensor-01/modules/SimulatedTemperatureSensor/telemetry/ambient?api-version=2022-05-31
+GET https://{your app subdomain}.azureiotcentral.com/api/devices/environmental-sensor-01/modules/SimulatedTemperatureSensor/telemetry/ambient?api-version=2022-07-31
 ```
 
 The response to this request looks like the following example:
@@ -171,7 +171,7 @@ The response to this request looks like the following example:
 Use the following request to retrieve the property values from a device that doesn't use components. In this example, the device is called `thermostat-01`:
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/devices/thermostat-01/properties?api-version=2022-05-31
+GET https://{your app subdomain}.azureiotcentral.com/api/devices/thermostat-01/properties?api-version=2022-07-31
 ```
 
 The response to this request looks like the following example. It shows the device is reporting a single property value:
@@ -190,7 +190,7 @@ The response to this request looks like the following example. It shows the devi
 Use the following request to retrieve property values from all components. In this example, the device is called `temperature-controller-01`:
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/devices/temperature-controller-01/properties?api-version=2022-05-31
+GET https://{your app subdomain}.azureiotcentral.com/api/devices/temperature-controller-01/properties?api-version=2022-07-31
 ```
 
 The response to this request looks like the following example:
@@ -261,7 +261,7 @@ The response to this request looks like the following example:
 Use the following request to retrieve a property value from an individual component. In this example, the device is called `temperature-controller-01` and the component is called `thermostat2`:
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/devices/temperature-controller-01/components/thermostat2/properties?api-version=2022-05-31
+GET https://{your app subdomain}.azureiotcentral.com/api/devices/temperature-controller-01/components/thermostat2/properties?api-version=2022-07-31
 ```
 
 The response to this request looks like the following example:
@@ -280,7 +280,7 @@ The response to this request looks like the following example:
 If the device is an IoT Edge device, use the following request to retrieve property values from a from a module. This example uses a device called `environmental-sensor-01` with a module called `SimulatedTemperatureSensor`:
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/devices/environmental-sensor-01/modules/SimulatedTemperatureSensor/properties?api-version=2022-05-31
+GET https://{your app subdomain}.azureiotcentral.com/api/devices/environmental-sensor-01/modules/SimulatedTemperatureSensor/properties?api-version=2022-07-31
 ```
 
 The response to this request looks like the following example:
@@ -310,7 +310,7 @@ Some properties are writable. For example, in the thermostat model the `targetTe
 Use the following request to write an individual property value to a device that doesn't use components. In this example, the device is called `thermostat-01`:
 
 ```http
-PATCH https://{your app subdomain}.azureiotcentral.com/api/devices/thermostat-01/properties?api-version=2022-05-31
+PATCH https://{your app subdomain}.azureiotcentral.com/api/devices/thermostat-01/properties?api-version=2022-07-31
 ```
 
 The request body looks like the following example:
@@ -339,7 +339,7 @@ The response to this request looks like the following example:
 Use the following request to write an individual property value to a device that does use components. In this example, the device is called `temperature-controller-01` and the component is called `thermostat2`:
 
 ```http
-PATCH https://{your app subdomain}.azureiotcentral.com/api/devices/temperature-controller-01/components/thermostat2/properties?api-version=2022-05-31
+PATCH https://{your app subdomain}.azureiotcentral.com/api/devices/temperature-controller-01/components/thermostat2/properties?api-version=2022-07-31
 ```
 
 The request body looks like the following example:
@@ -368,7 +368,7 @@ The response to this request looks like the following example:
 If the device is an IoT Edge device, use the following request to write an individual property value to a module. This example uses a device called `environmental-sensor-01`, a module called `SimulatedTemperatureSensor`, and a property called `SendInterval`:
 
 ```http
-PUT https://{your app subdomain}.azureiotcentral.com/api/devices/environmental-sensor-01/modules/SimulatedTemperatureSensor/properties?api-version=2022-05-31
+PUT https://{your app subdomain}.azureiotcentral.com/api/devices/environmental-sensor-01/modules/SimulatedTemperatureSensor/properties?api-version=2022-07-31
 ```
 
 The request body looks like the following example:
@@ -399,13 +399,13 @@ The response to this request looks like the following example:
 If you're using an IoT Edge device, use the following request to retrieve property values from a module:
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/devices/{deviceId}/modules/{moduleName}/properties?api-version=2022-05-31
+GET https://{your app subdomain}.azureiotcentral.com/api/devices/{deviceId}/modules/{moduleName}/properties?api-version=2022-07-31
 ```
 
 If you're using an IoT Edge device, use the following request to retrieve property values from a component in a module:
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/devices/{deviceId}/modules/{moduleName}/components/{componentName}/properties?api-version=2022-05-31
+GET https://{your app subdomain}.azureiotcentral.com/api/devices/{deviceId}/modules/{moduleName}/components/{componentName}/properties?api-version=2022-07-31
 ```
 
 ## Call commands
@@ -415,7 +415,7 @@ You can use the REST API to call device commands and retrieve the device history
 Use the following request to call a command on device that doesn't use components. In this example, the device is called `thermostat-01` and the command is called `getMaxMinReport`:
 
 ```http
-POST https://{your app subdomain}.azureiotcentral.com/api/devices/thermostat-01/commands/getMaxMinReport?api-version=2022-05-31
+POST https://{your app subdomain}.azureiotcentral.com/api/devices/thermostat-01/commands/getMaxMinReport?api-version=2022-07-31
 ```
 
 The request body looks like the following example:
@@ -444,7 +444,7 @@ The response to this request looks like the following example:
 To view the history for this command, use the following request:
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/devices/thermostat-01/commands/getMaxMinReport?api-version=2022-05-31
+GET https://{your app subdomain}.azureiotcentral.com/api/devices/thermostat-01/commands/getMaxMinReport?api-version=2022-07-31
 ```
 
 The response to this request looks like the following example:
@@ -469,15 +469,15 @@ The response to this request looks like the following example:
 Use the following request to call a command on device that does use components. In this example, the device is called `temperature-controller-01`, the component is called `thermostat2`, and the command is called `getMaxMinReport`:
 
 ```http
-POST https://{your app subdomain}.azureiotcentral.com/api/devices/temperature-controller-01/components/thermostat2/commands/getMaxMinReport?api-version=2022-05-31
+POST https://{your app subdomain}.azureiotcentral.com/api/devices/temperature-controller-01/components/thermostat2/commands/getMaxMinReport?api-version=2022-07-31
 ```
 
 The formats of the request payload and response are the same as for a device that doesn't use components.
 
 To view the history for this command, use the following request:
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/devices/temperature-controller-01/components/thermostat2/commands/getMaxMinReport?api-version=2022-05-31
+GET https://{your app subdomain}.azureiotcentral.com/api/devices/temperature-controller-01/components/thermostat2/commands/getMaxMinReport?api-version=2022-07-31
 ```
 
 > [!TIP]

articles/iot-central/core/howto-manage-device-templates-with-rest-api.md

@@ -43,7 +43,7 @@ The IoT Central REST API lets you:
 Use the following request to create and publish a new device template. Default views are automatically generated for device templates created this way.
 
 ```http
-PUT https://{subdomain}.{baseDomain}/api/deviceTemplates/{deviceTemplateId}?api-version=2022-05-31
+PUT https://{subdomain}.{baseDomain}/api/deviceTemplates/{deviceTemplateId}?api-version=2022-07-31
 ```
 
 >[!NOTE]
@@ -318,7 +318,7 @@ The response to this request looks like the following example:
 Use the following request to retrieve details of a device template from your application:
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/deviceTemplates/{deviceTemplateId}?api-version=2022-05-31
+GET https://{subdomain}.{baseDomain}/api/deviceTemplates/{deviceTemplateId}?api-version=2022-07-31
 ```
 
 >[!NOTE]
@@ -450,7 +450,7 @@ The response to this request looks like the following example:
 ## Update a device template
 
 ```http
-PATCH https://{subdomain}.{baseDomain}/api/deviceTemplates/{deviceTemplateId}?api-version=2022-05-31
+PATCH https://{subdomain}.{baseDomain}/api/deviceTemplates/{deviceTemplateId}?api-version=2022-07-31
 ```
 
 >[!NOTE]
@@ -726,15 +726,15 @@ The response to this request looks like the following example:
 Use the following request to delete a device template:
 
 ```http
-DELETE https://{subdomain}.{baseDomain}/api/deviceTemplates/{deviceTemplateId}?api-version=2022-05-31
+DELETE https://{subdomain}.{baseDomain}/api/deviceTemplates/{deviceTemplateId}?api-version=2022-07-31
 ```
 
 ## List device templates
 
 Use the following request to retrieve a list of device templates from your application:
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/deviceTemplates?api-version=2022-05-31
+GET https://{subdomain}.{baseDomain}/api/deviceTemplates?api-version=2022-07-31
 ```
 
 The response to this request looks like the following example: 

articles/iot-central/core/howto-manage-devices-with-rest-api.md

@@ -38,7 +38,7 @@ The IoT Central REST API lets you:
 Use the following request to create a new device.
 
 ```http
-PUT https://{subdomain}.{baseDomain}/api/devices/{deviceId}?api-version=2022-05-31
+PUT https://{subdomain}.{baseDomain}/api/devices/{deviceId}?api-version=2022-07-31
 ```
 
 The following example shows a request body that adds a device for a device template. You can get the `template` details from the device templates page in IoT Central application UI.
@@ -79,7 +79,7 @@ The response to this request looks like the following example:
 Use the following request to retrieve details of a device from your application:
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/devices/{deviceId}?api-version=2022-05-31
+GET https://{subdomain}.{baseDomain}/api/devices/{deviceId}?api-version=2022-07-31
 ```
 
 >[!NOTE]
@@ -104,7 +104,7 @@ The response to this request looks like the following example:
 Use the following request to retrieve credentials of a device from your application:
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/devices/{deviceId}/credentials?api-version=2022-05-31
+GET https://{subdomain}.{baseDomain}/api/devices/{deviceId}/credentials?api-version=2022-07-31
 ```
 
 The response to this request looks like the following example:
@@ -122,7 +122,7 @@ The response to this request looks like the following example:
 ### Update a device
 
 ```http
-PATCH https://{subdomain}.{baseDomain}/api/devices/{deviceId}?api-version=2022-05-31
+PATCH https://{subdomain}.{baseDomain}/api/devices/{deviceId}?api-version=2022-07-31
 ```
 
 >[!NOTE]
@@ -159,15 +159,15 @@ The response to this request looks like the following example:
 Use the following request to delete a device:
 
 ```http
-DELETE https://{subdomain}.{baseDomain}/api/devices/{deviceId}?api-version=2022-05-31
+DELETE https://{subdomain}.{baseDomain}/api/devices/{deviceId}?api-version=2022-07-31
 ```
 
 ### List devices
 
 Use the following request to retrieve a list of devices from your application:
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/devices?api-version=2022-05-31
+GET https://{subdomain}.{baseDomain}/api/devices?api-version=2022-07-31
 ```
 
 The response to this request looks like the following example: 
@@ -400,7 +400,7 @@ The response to this request looks like the following example:
 Use the following request to create a new device group.
 
 ```http
-PUT https://{subdomain}.{baseDomain}/api/deviceGroups/{deviceGroupId}?api-version=2022-05-31
+PUT https://{subdomain}.{baseDomain}/api/deviceGroups/{deviceGroupId}?api-version=2022-07-31
 ```
 
 When you create a device group, you define a `filter` that selects the devices to add to the group. A `filter` identifies a device template and any properties to match. The following example creates device group that contains all devices associated with the "dtmi:modelDefinition:dtdlv2" template where the `provisioned` property is true
@@ -444,7 +444,7 @@ The response to this request looks like the following example:
 Use the following request to retrieve details of a device group from your application:
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/deviceGroups/{deviceGroupId}?api-version=2022-05-31
+GET https://{subdomain}.{baseDomain}/api/deviceGroups/{deviceGroupId}?api-version=2022-07-31
 ```
 
 * deviceGroupId - Unique ID for the device group.
@@ -466,7 +466,7 @@ The response to this request looks like the following example:
 ### Update a device group
 
 ```http
-PATCH https://{subdomain}.{baseDomain}/api/deviceGroups/{deviceGroupId}?api-version=2022-05-31
+PATCH https://{subdomain}.{baseDomain}/api/deviceGroups/{deviceGroupId}?api-version=2022-07-31
 ```
 
 The sample request body looks like the following example which updates the `displayName` of the device group:
@@ -497,15 +497,15 @@ The response to this request looks like the following example:
 Use the following request to delete a device group:
 
 ```http
-DELETE https://{subdomain}.{baseDomain}/api/deviceGroups/{deviceGroupId}?api-version=2022-05-31
+DELETE https://{subdomain}.{baseDomain}/api/deviceGroups/{deviceGroupId}?api-version=2022-07-31
 ```
 
 ### List device groups
 
 Use the following request to retrieve a list of device groups from your application:
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/deviceGroups?api-version=2022-05-31
+GET https://{subdomain}.{baseDomain}/api/deviceGroups?api-version=2022-07-31
 ```
 
 The response to this request looks like the following example: