zulip/templates/zerver/help/include/webhook-url-with-bot-email.md

In the URL field, enter:

`{{ external_uri_scheme }}bot_email:bot_api_key@{{ api_url_scheme_relative }}{{ integration_url }}`

Replace `bot_email` and `bot_api_key` above with the URL-encoded email
address and API key of the bot.  To URL-encode the email address, you
just need to replace `@` in the bot's email address with `%40`.
templates: Add Markdown macro for URLs with bot_email@api_key. 2017-06-05 02:59:24 +02:00			`In the URL field, enter:`

template context: Give better names to the URLs for the API. The "subdomain" label is redundant, to the extent it's even accurate -- this is really just the URL we want to display, which may or may not involve a subdomain. Similarly "external". The former `external_api_path_subdomain` was never a path -- it's a host, followed by a path, which together form a scheme-relative URL. I'm not quite convinced that value is actually the right thing in 2 of the 3 places we use it, but fixing that can start by giving an accurate name to the thing we have. 2017-10-30 22:04:15 +01:00			`{{ external_uri_scheme }}bot_email:bot_api_key@{{ api_url_scheme_relative }}{{ integration_url }}`
templates: Add Markdown macro for URLs with bot_email@api_key. 2017-06-05 02:59:24 +02:00
markdown: Recommend substituting bot email and API key in URL. We now recommend substituting the appropriate bot email and API key in the webhook URL in the webhook-url-with-bot-email.md macro. 2017-06-14 05:02:17 +02:00			Replace `bot_email` and `bot_api_key` above with the URL-encoded email
			`address and API key of the bot. To URL-encode the email address, you`
			just need to replace `@` in the bot's email address with `%40`.