diff --git a/daprdocs/content/en/developing-applications/building-blocks/service-invocation/howto-invoke-discover-services.md b/daprdocs/content/en/developing-applications/building-blocks/service-invocation/howto-invoke-discover-services.md
index 571f49c2f..23a450559 100644
--- a/daprdocs/content/en/developing-applications/building-blocks/service-invocation/howto-invoke-discover-services.md
+++ b/daprdocs/content/en/developing-applications/building-blocks/service-invocation/howto-invoke-discover-services.md
@@ -111,6 +111,27 @@ curl http://localhost:3500/v1.0/invoke/cart/method/add -X DELETE
 ```
 
 Dapr puts any payload returned by the called service in the HTTP response's body.
+
+Furthermore, in order to avoid changing URL paths as much as possible, when make Dapr calls from user's code, Dapr provides a new way to help to integrate Dapr more easily:
+
+1. Change the address in the URL to `localhost:<dapr-http-port>`.
+2. Add a `dapr-app-id` header to specify the ID of the target service, or alternatively pass the ID via HTTP Basic Auth: `http://dapr-app-id:<service-id>@localhost:3500/path`.
+
+For example, the following command
+```bash
+curl http://localhost:3500/v1.0/invoke/cart/method/add
+```
+
+is equivalent with
+```bash
+curl -H 'dapr-app-id: cart' 'http://localhost:3500/add' -X POST
+```
+
+or
+```bash
+curl 'http://dapr-app-id:cart@localhost:3500/add' -X POST
+```
+
 {{% /codetab %}}
 
 {{% codetab %}}