Merge pull request #219264 from dominicbetts/central-api-versions

IoT Central: API version update

Author: prmerger-automator[bot]

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

@@ -46,7 +46,7 @@ The IoT Central REST API lets you:
 Use the following request to create a dashboard.
 
 ```http
-PUT https://{your app subdomain}.azureiotcentral.com/api/dashboards/{dashboardId}?api-version=2022-06-30-preview
+PUT https://{your app subdomain}.azureiotcentral.com/api/dashboards/{dashboardId}?api-version=2022-10-31-preview
 ```
 
 `dashboardId` - A unique [DTMI](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/dtdlv2.md#digital-twin-model-identifier) identifier for the dashboard.
@@ -246,7 +246,7 @@ The response to this request looks like the following example:
 Use the following request to retrieve the details of a dashboard by using a dashboard ID.
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/dashboards/{dashboardId}?api-version=2022-06-30-preview
+GET https://{your app subdomain}.azureiotcentral.com/api/dashboards/{dashboardId}?api-version=2022-10-31-preview
 ```
 
 The response to this request looks like the following example:
@@ -296,7 +296,7 @@ The response to this request looks like the following example:
 ## Update a dashboard
 
 ```http
-PATCH https://{your app subdomain}.azureiotcentral.com/api/dashboards/{dashboardId}?api-version=2022-06-30-preview
+PATCH https://{your app subdomain}.azureiotcentral.com/api/dashboards/{dashboardId}?api-version=2022-10-31-preview
 ```
 
 The following example shows a request body that updates the display name of a dashboard and size of the tile:
@@ -392,15 +392,15 @@ The response to this request looks like the following example:
 Use the following request to delete a dashboard by using the dashboard ID:
 
 ```http
-DELETE https://{your app subdomain}.azureiotcentral.com/api/dashboards/{dashboardId}?api-version=2022-06-30-preview
+DELETE https://{your app subdomain}.azureiotcentral.com/api/dashboards/{dashboardId}?api-version=2022-10-31-preview
 ```
 
 ## List dashboards
 
 Use the following request to retrieve a list of dashboards from your application:
 
 ```http
-GET https://{your app subdomain}.azureiotcentral.com/api/dashboards?api-version=2022-06-30-preview
+GET https://{your app subdomain}.azureiotcentral.com/api/dashboards?api-version=2022-10-31-preview
 ```
 
 The response to this request looks like the following example:

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

@@ -34,7 +34,7 @@ Each data export definition can send data to one or more destinations. Create th
 Use the following request to create or update a destination definition:
 
 ```http
-PUT https://{subdomain}.{baseDomain}/api/dataExport/destinations/{destinationId}?api-version=2022-06-30-preview
+PUT https://{subdomain}.{baseDomain}/api/dataExport/destinations/{destinationId}?api-version=2022-10-31-preview
 ```
 
 * destinationId - Unique ID for the destination.
@@ -75,7 +75,7 @@ The response to this request looks like the following example:
 Use the following request to retrieve details of a destination from your application:
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/dataExport/destinations/{destinationId}?api-version=2022-06-30-preview
+GET https://{subdomain}.{baseDomain}/api/dataExport/destinations/{destinationId}?api-version=2022-10-31-preview
 ```
 
 The response to this request looks like the following example:
@@ -96,7 +96,7 @@ The response to this request looks like the following example:
 Use the following request to retrieve a list of destinations from your application:
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/dataExport/destinations?api-version=2022-06-30-preview
+GET https://{subdomain}.{baseDomain}/api/dataExport/destinations?api-version=2022-10-31-preview
 ```
 
 The response to this request looks like the following example: 
@@ -131,7 +131,7 @@ The response to this request looks like the following example:
 ### Patch a destination
 
 ```http
-PATCH https://{subdomain}.{baseDomain}/api/dataExport/destinations/{destinationId}?api-version=2022-06-30-preview
+PATCH https://{subdomain}.{baseDomain}/api/dataExport/destinations/{destinationId}?api-version=2022-10-31-preview
 ```
 
 You can use this to perform an incremental update to an export. The sample request body looks like the following example that updates the `displayName` to a destination:
@@ -163,15 +163,15 @@ The response to this request looks like the following example:
 Use the following request to delete a destination:
 
 ```http
-DELETE https://{subdomain}.{baseDomain}/api/dataExport/destinations/{destinationId}?api-version=2022-06-30-preview
+DELETE https://{subdomain}.{baseDomain}/api/dataExport/destinations/{destinationId}?api-version=2022-10-31-preview
 ```
 
 ### Create or update an export definition
 
 Use the following request to create or update a data export definition:
 
 ```http
-PUT https://{subdomain}.{baseDomain}/api/dataExport/exports/{exportId}?api-version=2022-06-30-preview
+PUT https://{subdomain}.{baseDomain}/api/dataExport/exports/{exportId}?api-version=2022-10-31-preview
 ```
 
 The following example shows a request body that creates an export definition for device telemetry:
@@ -233,7 +233,7 @@ The response to this request looks like the following example:
 Use the following request to retrieve details of an export definition from your application:
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/dataExport/exports/{exportId}?api-version=2022-06-30-preview
+GET https://{subdomain}.{baseDomain}/api/dataExport/exports/{exportId}?api-version=2022-10-31-preview
 ```
 
 The response to this request looks like the following example:
@@ -254,7 +254,7 @@ The response to this request looks like the following example:
 Use the following request to retrieve a list of export definitions from your application:
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/dataExport/exports?api-version=2022-06-30-preview
+GET https://{subdomain}.{baseDomain}/api/dataExport/exports?api-version=2022-10-31-preview
 ```
 
 The response to this request looks like the following example: 
@@ -303,7 +303,7 @@ The response to this request looks like the following example:
 ### Patch an export definition
 
 ```http
-PATCH https://{subdomain}.{baseDomain}/dataExport/exports/{exportId}?api-version=2022-06-30-preview
+PATCH https://{subdomain}.{baseDomain}/dataExport/exports/{exportId}?api-version=2022-10-31-preview
 ```
 
 You can use this to perform an incremental update to an export. The sample request body looks like the following example that updates the `enrichments` to an export:
@@ -353,7 +353,7 @@ The response to this request looks like the following example:
 Use the following request to delete an export definition:
 
 ```http
-DELETE https://{subdomain}.{baseDomain}/api/dataExport/destinations/{destinationId}?api-version=2022-06-30-preview
+DELETE https://{subdomain}.{baseDomain}/api/dataExport/destinations/{destinationId}?api-version=2022-10-31-preview
 ```
 
 ## Next steps

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

@@ -37,7 +37,7 @@ To learn how to query devices by using the IoT Central UI, see [How to use data
 Use the following request to run a query:
 
 ```http
-POST https://{your app subdomain}.azureiotcentral.com/api/query?api-version=2022-06-30-preview
+POST https://{your app subdomain}.azureiotcentral.com/api/query?api-version=2022-10-31-preview
 ```
 
 The query is in the request body and looks like the following example: