Merge pull request #209875 from v-krishnag/restjobsapi

Restjobsapi

Author: v-regandowner

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=1.2-preview
+PUT https://{subdomain}.{baseDomain}/api/dataExport/destinations/{destinationId}?api-version=2022-06-30-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=1.2-preview
+GET https://{subdomain}.{baseDomain}/api/dataExport/destinations/{destinationId}?api-version=2022-06-30-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=1.2-preview
+GET https://{subdomain}.{baseDomain}/api/dataExport/destinations?api-version=2022-06-30-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=1.2-preview
+PATCH https://{subdomain}.{baseDomain}/api/dataExport/destinations/{destinationId}?api-version=2022-06-30-preview
 ```
 
 You can use this to perform an incremental update to an export. The sample request body looks like the following example which 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=1.2-preview
+DELETE https://{subdomain}.{baseDomain}/api/dataExport/destinations/{destinationId}?api-version=2022-06-30-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=1.2-preview
+PUT https://{subdomain}.{baseDomain}/api/dataExport/exports/{exportId}?api-version=2022-06-30-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=1.2-preview
+GET https://{subdomain}.{baseDomain}/api/dataExport/exports/{exportId}?api-version=2022-06-30-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=1.2-preview
+GET https://{subdomain}.{baseDomain}/api/dataExport/exports?api-version=2022-06-30-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=1.2-preview
+PATCH https://{subdomain}.{baseDomain}/dataExport/exports/{exportId}?api-version=2022-06-30-preview
 ```
 
 You can use this to perform an incremental update to an export. The sample request body looks like the following example which 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=1.2-preview
+DELETE https://{subdomain}.{baseDomain}/api/dataExport/destinations/{destinationId}?api-version=2022-06-30-preview
 ```
 
 ## Next steps

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

@@ -986,17 +986,14 @@ The response to this request looks like the following example:
 
 You can use ODATA filters to filter the results returned by the list device templates API.
 
-> [!NOTE]
-> Currently, ODATA support is only available for `api-version=1.2-preview`.
-
 ### $top
 
 Use the **$top** filter to set the result size. The maximum returned result size is 100, and the default size is 25.
 
 Use the following request to retrieve the top 10 device templates from your application:
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/deviceTemplates?api-version=1.2-preview&$top=10
+GET https://{subdomain}.{baseDomain}/api/deviceTemplates?api-version=2022-07-31&$top=10
 ```
 
 The response to this request looks like the following example:
@@ -1050,7 +1047,7 @@ The response to this request looks like the following example:
         },
         ...
     ],
-    "nextLink": "https://custom-12qmyn6sm0x.azureiotcentral.com/api/deviceTemplates?api-version=1.2-preview&%24top=1&%24skiptoken=%7B%22token%22%3A%22%2BRID%3A%7EJWYqAKZQKp20qCoAAAAACA%3D%3D%23RT%3A1%23TRC%3A1%23ISV%3A2%23IEO%3A65551%23QCF%3A4%22%2C%22range%22%3A%7B%22min%22%3A%2205C1DFFFFFFFFC%22%2C%22max%22%3A%22FF%22%7D%7D"
+    "nextLink": "https://custom-12qmyn6sm0x.azureiotcentral.com/api/deviceTemplates?api-version=2022-07-31&%24top=1&%24skiptoken=%7B%22token%22%3A%22%2BRID%3A%7EJWYqAKZQKp20qCoAAAAACA%3D%3D%23RT%3A1%23TRC%3A1%23ISV%3A2%23IEO%3A65551%23QCF%3A4%22%2C%22range%22%3A%7B%22min%22%3A%2205C1DFFFFFFFFC%22%2C%22max%22%3A%22FF%22%7D%7D"
 }
 ```
 
@@ -1097,7 +1094,7 @@ $filter=contains(displayName, 'template1) eq false
 The following example shows how to retrieve all the device templates where the display name contains the string `thermostat`:
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/deviceTemplates?api-version=1.2-preview&$filter=contains(displayName, 'thermostat')
+GET https://{subdomain}.{baseDomain}/api/deviceTemplates?api-version=2022-07-31&$filter=contains(displayName, 'thermostat')
 ```
 
 The response to this request looks like the following example:
@@ -1187,7 +1184,7 @@ $orderby=displayName desc
 The following example shows how to retrieve all the device templates where the result is sorted by `displayName` :
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/deviceTemplates?api-version=1.2-preview&$orderby=displayName
+GET https://{subdomain}.{baseDomain}/api/deviceTemplates?api-version=2022-07-31&$orderby=displayName
 ```
 
 The response to this request looks like the following example:
@@ -1270,7 +1267,7 @@ You can also combine two or more filters.
 The following example shows how to retrieve the top 2 device templates where the display name contains the string `thermostat`.
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/deviceTemplates?api-version=1.2-preview&$filter=contains(displayName, 'thermostat')&$top=2
+GET https://{subdomain}.{baseDomain}/api/deviceTemplates?api-version=2022-07-31&$filter=contains(displayName, 'thermostat')&$top=2
 ```
 
 The response to this request looks like the following example:

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

@@ -201,17 +201,14 @@ The response to this request looks like the following example:
 
 You can use ODATA filters to filter the results returned by the list devices API.
 
-> [!NOTE]
-> Currently, ODATA support is only available for `api-version=1.2-preview`
-
 ### $top
 
 Use the **$top** to set the result size, the maximum returned result size is 100, the default size is 25.
 
 Use the following request to retrieve a top 10 device from your application:
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/devices?api-version=1.2-preview&$top=10
+GET https://{subdomain}.{baseDomain}/api/devices?api-version=2022-07-31&$top=10
 ```
 
 The response to this request looks like the following example:
@@ -239,7 +236,7 @@ The response to this request looks like the following example:
         },
         ...
     ],
-    "nextLink": "https://custom-12qmyn6sm0x.azureiotcentral.com/api/devices?api-version=1.2-preview&%24top=1&%24skiptoken=%257B%2522token%2522%253A%2522%252BRID%253A%7EJWYqAOis7THQbBQAAAAAAg%253D%253D%2523RT%253A1%2523TRC%253A1%2523ISV%253A2%2523IEO%253A65551%2523QCF%253A4%2522%252C%2522range%2522%253A%257B%2522min%2522%253A%2522%2522%252C%2522max%2522%253A%252205C1D7F7591D44%2522%257D%257D"
+    "nextLink": "https://custom-12qmyn6sm0x.azureiotcentral.com/api/devices?api-version=2022-07-31&%24top=1&%24skiptoken=%257B%2522token%2522%253A%2522%252BRID%253A%7EJWYqAOis7THQbBQAAAAAAg%253D%253D%2523RT%253A1%2523TRC%253A1%2523ISV%253A2%2523IEO%253A65551%2523QCF%253A4%2522%252C%2522range%2522%253A%257B%2522min%2522%253A%2522%2522%252C%2522max%2522%253A%252205C1D7F7591D44%2522%257D%257D"
 }
 ```
 
@@ -254,10 +251,10 @@ Use **$filter** to create expressions that filter the list of devices. The follo
 | -------------------- | ------ | --------------------------------------- |
 | Equals               | eq     | id eq 'device1' and scopes eq 'redmond' |
 | Not Equals           | ne     | Enabled ne true                         |
-| Less than or equals       | le     | indexof(displayName, 'device1') le -1   |
-| Less than            | lt     | indexof(displayName, 'device1') lt 0    |
-| Greater than or equals      | ge     | indexof(displayName, 'device1') ge 0    |
-| Greater than           | gt     | indexof(displayName, 'device1') gt 0    |
+| Less than or equals       | le     | contains(displayName, 'device1') le -1   |
+| Less than            | lt     | contains(displayName, 'device1') lt 0    |
+| Greater than or equals      | ge     | contains(displayName, 'device1') ge 0    |
+| Greater than           | gt     | contains(displayName, 'device1') gt 0    |
 
 The following table shows the logic operators you can use in *$filter* expressions:
 
@@ -280,16 +277,16 @@ Currently, *$filter* works with the following device fields:
 
 **$filter supported functions:**
 
-Currently, the only supported filter function for device lists is the `indexof` function:
+Currently, the only supported filter function for device lists is the `contains` function:
 
 ```
-$filter=indexof(displayName, 'device1') ge 0
+$filter=contains(displayName, 'device1') ge 0
 ```
 
-The following example shows how to retrieve all the devices where the display name has index the string `thermostat`:
+The following example shows how to retrieve all the devices where the display name contains the string `thermostat`:
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/deviceTemplates?api-version=1.2-preview&$filter=index(displayName, 'thermostat')
+GET https://{subdomain}.{baseDomain}/api/deviceTemplates?api-version=2022-07-31&$filter=contains(displayName, 'thermostat')
 ```
 
 The response to this request looks like the following example:
@@ -331,7 +328,7 @@ $orderby=displayName desc
 The following example shows how to retrieve all the device templates where the result is sorted by `displayName` :
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/devices?api-version=1.2-preview&$orderby=displayName
+GET https://{subdomain}.{baseDomain}/api/devices?api-version=2022-07-31&$orderby=displayName
 ```
 
 The response to this request looks like the following example:
@@ -366,7 +363,7 @@ You can also combine two or more filters.
 The following example shows how to retrieve the top 2 device where the display name contains the string `thermostat`.
 
 ```http
-GET https://{subdomain}.{baseDomain}/api/deviceTemplates?api-version=1.2-preview&$filter=contains(displayName, 'thermostat')&$top=2
+GET https://{subdomain}.{baseDomain}/api/deviceTemplates?api-version=2022-07-31&$filter=contains(displayName, 'thermostat')&$top=2
 ```
 
 The response to this request looks like the following example: