Replace Postman in API article

Author: baanders

articles/digital-twins/.openpublishing.redirection.digital-twins.json

@@ -1,10 +1,5 @@
 {
   "redirections": [
-    {
-      "source_path": "how-to-use-postman-with-digital-twins.md",
-      "redirect_url": "/azure/digital-twins/how-to-use-apis",
-      "redirect_document_id": true
-    },
     {
       "source_path": "how-to-manage-routes.md",
       "redirect_url": "/azure/digital-twins/how-to-create-routes",
@@ -190,6 +185,11 @@
       "redirect_url": "https://github.com/Azure-Samples/digital-twins-samples/tree/master/scripts",
       "redirect_document_id": false
     },
+    {
+      "source_path": "how-to-use-postman-with-digital-twins.md",
+      "redirect_url": "/azure/digital-twins/how-to-use-apis",
+      "redirect_document_id": true
+    },
     {
       "source_path": "how-to-configure-postman.md",
       "redirect_url": "/azure/digital-twins/how-to-use-apis",

articles/digital-twins/concepts-apis-sdks.md

@@ -48,7 +48,7 @@ Here's some general information for calling the Azure Digital Twins APIs directl
 * Azure Digital Twins doesn't currently support Cross-Origin Resource Sharing (CORS). For more info about the impact and resolution strategies, see [Cross-Origin Resource Sharing (CORS) for Azure Digital Twins](concepts-security.md#cross-origin-resource-sharing-cors).
 
 Here's some more information about authentication for API requests.
-* One way to generate a bearer token for Azure Digital Twins API requests is with the [az account get-access-token](/cli/azure/account#az-account-get-access-token()) CLI command. For detailed instructions, see [Get bearer token](how-to-use-apis.md#get-bearer-token).
+* One way to generate a bearer token for Azure Digital Twins API requests is with the [az account get-access-token](/cli/azure/account#az-account-get-access-token()) CLI command. For detailed instructions, see [Get bearer token](how-to-use-apis.md#add-bearer-token).
 * Requests to the Azure Digital Twins APIs require a user or service principal that is a part of the same [Microsoft Entra ID](../active-directory/fundamentals/active-directory-whatis.md)  tenant where the Azure Digital Twins instance exists. To prevent malicious scanning of Azure Digital Twins endpoints, requests with access tokens from outside the originating tenant will be returned a "404 Sub-Domain not found" error message. This error will be returned even if the user or service principal was given an Azure Digital Twins Data Owner or Azure Digital Twins Data Reader role through [Microsoft Entra B2B](../active-directory/external-identities/what-is-b2b.md) collaboration. For information on how to achieve access across multiple tenants, see [Write app authentication code](how-to-authenticate-client.md#authenticate-across-tenants).
 
 ### SDK notes
@@ -101,7 +101,7 @@ You'll also need to grant the following **RBAC permissions** to the system-assig
 * [Storage Blob Data Reader](../role-based-access-control/built-in-roles.md#storage-blob-data-reader) for the Azure Storage input blob container
 * [Storage Blob Data Contributor](../role-based-access-control/built-in-roles.md#storage-blob-data-contributor) for the Azure Storage output blob container
 
-Finally, generate a bearer token that can be used in your requests to the Jobs API. For instructions, see [Get bearer token](how-to-use-apis.md#get-bearer-token).
+Finally, generate a bearer token that can be used in your requests to the Jobs API. For instructions, see [Get bearer token](how-to-use-apis.md#add-bearer-token).
 
 ### Format data 
 
@@ -164,7 +164,7 @@ Keep the following considerations in mind while working with the Import Jobs API
 The [Delete Jobs API](/rest/api/digital-twins/dataplane/jobs) is a data plane API that allows you to delete all models, twins, and relationships in an instance with a single API call. Delete Jobs API operations are also available as [CLI commands](/cli/azure/dt/job/deletion). Visit the API documentation to see the request details for creating a delete job and checking its status.
 
 To make sure all elements are deleted, follow these recommendations while using the Delete Jobs API:
-* For instructions on how to generate a bearer token to authenticate API requests, see [Get bearer token](how-to-use-apis.md#get-bearer-token).
+* For instructions on how to generate a bearer token to authenticate API requests, see [Get bearer token](how-to-use-apis.md#add-bearer-token).
 * If you recently imported a large number of entities to your graph, wait for some time and verify that all elements are synchronized in your graph before beginning the delete job.
 * Stop all operations on the instance, especially upload operations, until the delete job is complete.