From 6719f56f12b807ab657b8af159f890b9e1a0cfe6 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 14 Aug 2026 13:09:56 +0000 Subject: [PATCH] docs: clarify triple-bracket env vars and note JSM Operations via webhook --- detect/synthetic-monitoring/api-checks/configuration.mdx | 6 ++++++ integrations/alerts/webhooks.mdx | 4 +++- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/detect/synthetic-monitoring/api-checks/configuration.mdx b/detect/synthetic-monitoring/api-checks/configuration.mdx index 6977306c..272aacc7 100644 --- a/detect/synthetic-monitoring/api-checks/configuration.mdx +++ b/detect/synthetic-monitoring/api-checks/configuration.mdx @@ -101,6 +101,12 @@ Variables can be used in the following API checks fields: - Query parameters values - Basic authentication username and password +#### Preserving special characters with triple brackets + +Double-bracket references are encoded before the request is sent. Characters such as `&`, `<`, `>`, `"`, and `'` are replaced with their encoded equivalents (for example, `&` becomes `&`). This can break header values, API keys, and tokens that must be sent verbatim. + +Use triple brackets when the raw value must reach the target server unchanged. For example, if the value of an `X-API-Key` header stored in `USER_API_KEY` contains an ampersand, reference it as `{{{USER_API_KEY}}}` in the header value so the ampersand is not encoded. + ### Using helpers and built-in variables Next to your own variables, we've added some built-in ones. diff --git a/integrations/alerts/webhooks.mdx b/integrations/alerts/webhooks.mdx index 254864fc..c9ad5b69 100644 --- a/integrations/alerts/webhooks.mdx +++ b/integrations/alerts/webhooks.mdx @@ -268,7 +268,9 @@ This means that for checks on a 1 minute schedule, there is a potential overlap The following examples give an idea how to integrate Checkly with 3rd party alerting and issue tracking systems. -### OpsGenie +### OpsGenie and Jira Service Management (JSM) Operations + +Checkly does not ship a dedicated JSM Operations alert channel. Because JSM Operations is built on the OpsGenie alerts API, the same webhook pattern shown below works for both. Point the webhook URL at your JSM Operations alerts endpoint instead of the OpsGenie one, keep the payload as-is, and authenticate with the API key issued by JSM. You can create an OpsGenie