From 5459c96033ac53ab612ab08a5ac62ae643960e12 Mon Sep 17 00:00:00 2001 From: joshvanl Date: Fri, 22 Aug 2025 17:56:31 -0300 Subject: [PATCH] [1.16] Adds not about new SA headers Adds docs on Service Invocation app ID & namespace headers. Fixes https://github.com/dapr/docs/issues/4816 Signed-off-by: joshvanl --- .../en/reference/api/service_invocation_api.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/daprdocs/content/en/reference/api/service_invocation_api.md b/daprdocs/content/en/reference/api/service_invocation_api.md index 855195110..d4cfa9401 100644 --- a/daprdocs/content/en/reference/api/service_invocation_api.md +++ b/daprdocs/content/en/reference/api/service_invocation_api.md @@ -134,6 +134,17 @@ In case you are invoking `mathService` on a different namespace, you can use the In this URL, `testing` is the namespace that `mathService` is running in. +### Headers in Service Invocation Requests + +When Dapr invokes a service, it automatically adds the following headers to the request: + +| Header | Description | Example | +|--------|-------------|---------| +| `dapr-app-id` | The ID of the calling application | `myapp` | +| `dapr-caller-namespace` | The namespace of the calling application | `production` | + +These headers are available in both HTTP and gRPC service invocation requests. + #### Non-Dapr Endpoint Example If the `mathService` service was a non-Dapr application, then it could be invoked using service invocation via an `HTTPEndpoint`, as well as a Fully Qualified Domain Name (FQDN) URL.