From 1b799c539de649a9fb0f1462c509c7a37a750261 Mon Sep 17 00:00:00 2001
From: Fi Quick <47183728+fiquick@users.noreply.github.com>
Date: Wed, 17 Sep 2025 14:41:52 +0100
Subject: [PATCH] IP filtering via API

---
 modules/ROOT/pages/security/ip-filtering.adoc | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/modules/ROOT/pages/security/ip-filtering.adoc b/modules/ROOT/pages/security/ip-filtering.adoc
index 2e0622ac2..1b71ffa90 100644
--- a/modules/ROOT/pages/security/ip-filtering.adoc
+++ b/modules/ROOT/pages/security/ip-filtering.adoc
@@ -94,3 +94,8 @@ With IP filtering:
 To use `neo4j-admin database upload` add the specific link:https://support.neo4j.com/s/article/360050504254-What-are-the-public-IP-addresses-to-provision-in-a-firewall-configuration-to-allow-Aura-use[Control Plane Egress] to your IP filter allow list. 
 This ensures the temporary connection needed to push data is permitted.
 
+== IP filtering via API
+
+IP filtering can also be achieved via API, as described in link:{neo4j-docs-base-uri}/aura/platform/api/specification/?urls.primaryName=Aura%20v2beta1#/[Aura API specification].
+Note that this is only available with v2beta1.
+