From b6ce93e029a8f0aecbbdcdc8ed7383156fede6e7 Mon Sep 17 00:00:00 2001 From: Rhea Parekh Date: Fri, 20 Jul 2018 15:19:14 +0530 Subject: [PATCH] outgoing webhooks: Fix sample values for slack outgoing webhooks. This switches us to use the correct timestamp, service_id and token formats. The 'service_id' should be the ID of the bot user. The token should be a sample token generated from 'random_api_key()'. --- templates/zerver/api/outgoing-webhooks.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/templates/zerver/api/outgoing-webhooks.md b/templates/zerver/api/outgoing-webhooks.md index 2dd9b4b50b..3b96b9ec85 100644 --- a/templates/zerver/api/outgoing-webhooks.md +++ b/templates/zerver/api/outgoing-webhooks.md @@ -174,17 +174,17 @@ webhook expects: The above data is posted as list of tuples (not JSON), here's an example: ``` -[('token', 'abcdef'), +[('token', 'v9fpCdldZIej2bco3uoUvGp06PowKFOf'), ('team_id', 'zulip'), ('team_domain', 'zulip.com'), ('channel_id', '123'), ('channel_name', 'integrations'), - ('timestamp', 123456), + ('timestamp', 1532078950), ('user_id', 21), ('user_name', 'Sample User'), ('text', '@**test**'), ('trigger_word', 'mention'), - ('service_id', None)] + ('service_id', 27)] ``` * For successful request, if data is returned, it returns that data,