Merge pull request #169808 from dominicbetts/central-rest-api-links

Update API links

Author: PRMerger9

articles/iot-central/core/howto-export-data-legacy.md

@@ -550,7 +550,7 @@ This example snapshot shows a message that contains device and properties data i
 
 If you have an existing data export in your preview application with the *Devices* and *Device templates* streams turned on, update your export by **30 June 2020**. This requirement applies to exports to Azure Blob storage, Azure Event Hubs, and Azure Service Bus.
 
-Starting 3 February 2020, all new exports in applications with Devices and Device templates enabled will have the data format described above. All exports created before this date remain on the old data format until 30 June 2020, at which time these exports will automatically be migrated to the new data format. The new data format matches the [device](/rest/api/iotcentral/2021-04-30preview/devices/get), [device property](/rest/api/iotcentral/2021-04-30preview/devices/getproperties), [device cloud property](/rest/api/iotcentral/2021-04-30preview/devices/getcloudproperties), and [device template](/rest/api/iotcentral/2021-04-30preview/devicetemplates/get) objects in the IoT Central public API.
+Starting 3 February 2020, all new exports in applications with Devices and Device templates enabled will have the data format described above. All exports created before this date remain on the old data format until 30 June 2020, at which time these exports will automatically be migrated to the new data format. The new data format matches the [device](/rest/api/iotcentral/1.0/devices/get), [device property](/rest/api/iotcentral/1.0/devices/get-properties),  and [device template](/rest/api/iotcentral/1.0/device-templates/get) objects in the IoT Central public API.
 
 For **Devices**, notable differences between the old data format and the new data format include:
 - `@id` for device is removed, `deviceId` is renamed to `id`