diff --git a/docs/serverless/rules/detection-engine-overview.asciidoc b/docs/serverless/rules/detection-engine-overview.asciidoc
index 3d89447e5c..f3d421295b 100644
--- a/docs/serverless/rules/detection-engine-overview.asciidoc
+++ b/docs/serverless/rules/detection-engine-overview.asciidoc
@@ -41,7 +41,7 @@ After rules have started running, you can monitor their executions to verify
 they are functioning correctly, as well as view, manage, and troubleshoot
 alerts (see <<security-alerts-manage,Manage detection alerts>> and <<security-alerts-ui-monitor,Monitor and troubleshoot rule executions>>).
 
-You can create and manage rules and alerts via the UI or the {security-guide}/rule-api-overview.html[Detections API].
+You can create and manage rules and alerts via the UI or the https://www.elastic.co/docs/api/doc/kibana/group/endpoint-security-detections-api[Detections API].
 
 // Link to classic docs until serverless API docs are available.
 
diff --git a/docs/serverless/rules/rules-ui-create.asciidoc b/docs/serverless/rules/rules-ui-create.asciidoc
index f5f0468141..f6a80bd324 100644
--- a/docs/serverless/rules/rules-ui-create.asciidoc
+++ b/docs/serverless/rules/rules-ui-create.asciidoc
@@ -793,7 +793,7 @@ The following variables can only be passed if the rule’s action frequency is f
 [[placeholder-examples]]
 ==== Alert placeholder examples
 
-To understand which fields to parse, see the {security-guide}/rule-api-overview.html[Detections API] to view the JSON representation of rules.
+To understand which fields to parse, see the https://www.elastic.co/docs/api/doc/kibana/group/endpoint-security-detections-api[Detections API] to view the JSON representation of rules.
 
 // Link to classic docs until serverless API docs are available.