From c6775c1b2573125c519f0ad58fa063fd2caa8d16 Mon Sep 17 00:00:00 2001 From: Jan-Philipp Benecke Date: Wed, 9 Jul 2025 20:37:37 +0200 Subject: [PATCH] Add headers to REST command response documentation (#39938) --- source/_integrations/rest_command.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_integrations/rest_command.markdown b/source/_integrations/rest_command.markdown index 7b9ba7bec03..ed207a711ff 100644 --- a/source/_integrations/rest_command.markdown +++ b/source/_integrations/rest_command.markdown @@ -100,7 +100,8 @@ rest_command: ### Using REST command Response in automations -REST commands provide an action response in a dictionary containing `status` (containing the HTTP response code) and `content` containing the response body as text or JSON. This response can be accessed in automations using [`response_variable`](/docs/scripts/perform-actions#use-templates-to-handle-response-data). +REST commands provide an action response in a dictionary containing `status` (containing the HTTP response code), `content` containing the response body as text or JSON and `headers` containing the response headers. +This response can be accessed in automations using [`response_variable`](/docs/scripts/perform-actions#use-templates-to-handle-response-data). The following example shows how the REST command response may be used in automations. In this case, checking the [Traefik API](https://doc.traefik.io/traefik/operations/api/) for errors.