From a33ca94c076d8099d65ad0095f2d177c9c612d07 Mon Sep 17 00:00:00 2001 From: Katheryn Satterlee Date: Thu, 10 Apr 2025 16:41:26 -0500 Subject: [PATCH] Update what-api-endpoints-to-expose-to-the-public-internet.md (#27977) Resolves #27491 --- .../what-api-endpoints-to-expose-to-the-public-internet.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/what-api-endpoints-to-expose-to-the-public-internet.md b/articles/what-api-endpoints-to-expose-to-the-public-internet.md index 6550432994..76b50787a6 100644 --- a/articles/what-api-endpoints-to-expose-to-the-public-internet.md +++ b/articles/what-api-endpoints-to-expose-to-the-public-internet.md @@ -6,8 +6,8 @@ This guide details which API endpoints to make publicly accessible. If you would like to manage hosts that can travel outside your VPN or intranet, we recommend only exposing the osquery endpoints to the public internet: -- `/api/osquery` -- `/api/v1/osquery` +- `/api/osquery/*` +- `/api/v1/osquery/*` ## Using Fleet Desktop on remote devices