From 7183c9aaab7b2e76880cfd89e098d3d7b719de32 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Fri, 10 Jul 2026 13:08:56 +0000
Subject: [PATCH] docs: clarify URL monitor limits and add UI steps for
 creating groups

---
 detect/uptime-monitoring/url-monitors/overview.mdx | 4 ++++
 platform/groups.mdx                                | 9 +++++++++
 2 files changed, 13 insertions(+)

diff --git a/detect/uptime-monitoring/url-monitors/overview.mdx b/detect/uptime-monitoring/url-monitors/overview.mdx
index 09fbd58d..8ea56ecc 100644
--- a/detect/uptime-monitoring/url-monitors/overview.mdx
+++ b/detect/uptime-monitoring/url-monitors/overview.mdx
@@ -34,6 +34,10 @@ URL monitors track the availability of your HTTP-based services by sending reque
 * Checking that your SSL certificate is still valid
 * Confirming that a public pricing endpoint is reachable for customers
 
+<Note>
+URL monitors always send a plain `GET` request. They do not support custom request headers, cookies, request bodies, authentication, or [dynamic variables](/detect/synthetic-monitoring/api-checks/configuration) such as `{{moment}}`. If you need any of those, use an [API check](/detect/synthetic-monitoring/api-checks/overview) instead — API checks support all HTTP methods, custom headers (including `Cookie`), request bodies, and body/header assertions.
+</Note>
+
 ## How URL Monitors Work
 
 URL monitors send HTTP requests to specified URLs and validate availability and performance. They can be configured to check for specific status codes and response times while running from multiple global locations.
diff --git a/platform/groups.mdx b/platform/groups.mdx
index 276b5a85..80c952b1 100644
--- a/platform/groups.mdx
+++ b/platform/groups.mdx
@@ -15,6 +15,15 @@ You can populate a group by moving existing checks into it or by creating new ch
 
 <Note>By default, newly created check groups behave like folders, with no group-level configuration applied. To get started:</Note>
 
+## Creating a group in the UI
+
+1. In the Checkly app, open the **Checks** page from the left sidebar.
+2. Click the **New check** dropdown in the top right and select **Group**.
+3. Give the group a name, then click **Save**.
+4. Add checks to the group either by opening an existing check and setting its **Group** field, or by creating a new check from within the group.
+
+To manage groups as code, see the [CheckGroup construct](/constructs/check-group) for the Checkly CLI or the [`checkly_check_group` resource](/integrations/iac/terraform/overview) for Terraform.
+
 ## Configuration
 
 Groups let you apply shared configuration to standardize how checks behave. Group-level configurations override check-level settings when applied.