From 9bd32c7567d177c4812651ede6b408403eddb34a Mon Sep 17 00:00:00 2001 From: Chris Browet Date: Mon, 26 Jul 2021 10:23:41 +0200 Subject: [PATCH] Fix webhook trigger.json example (#18613) As it is, the curl sample, without data, actually generates a ``` json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) ``` --- source/_docs/automation/trigger.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown index 575940fb076..50fc254e8c1 100644 --- a/source/_docs/automation/trigger.markdown +++ b/source/_docs/automation/trigger.markdown @@ -667,7 +667,7 @@ automation: You can run this automation by sending an HTTP POST request to `http://your-home-assistant:8123/api/webhook/some_hook_id`. Here is an example using the **curl** command line program, with an empty data payload: ```shell -curl -X POST https://your-home-assistant:8123/api/webhook/some_hook_id +curl -X POST -d '{ "key": "value"}' https://your-home-assistant:8123/api/webhook/some_hook_id ``` Webhook endpoints don't require authentication, other than knowing a valid webhook ID. You can send a data payload, either as encoded form data or JSON data. The payload is available in an automation template as either `trigger.json` or `trigger.data`. URL query parameters are available in the template as `trigger.query`. Remember to use an HTTPS URL if you've secured your Home Assistant installation with SSL/TLS.