diff --git a/3.9/release-notes-api-changes39.md b/3.9/release-notes-api-changes39.md
index c1407f6082..2713618715 100644
--- a/3.9/release-notes-api-changes39.md
+++ b/3.9/release-notes-api-changes39.md
@@ -23,6 +23,8 @@ integrations for ArangoDB 3.9.
 
 ### Endpoints removed
 
+#### Export API
+
 The REST API endpoint `/_api/export` has been removed in ArangoDB 3.9.
 This endpoint was previously only present in single server, but never
 supported in cluster deployments.
@@ -44,4 +46,22 @@ in ArangoDB 3.8 and is now removed. If the functionality is still required
 by client applications, running a streaming AQL query can be used as a
 substitution.
 
+#### Redirects
+
+Since ArangoDB 3.7, some cluster APIs were made available under different
+paths. The old paths were left in place and simply redirected to the new
+address. These redirects have now been removed in ArangoDB 3.9.
+
+The following list shows the old, now dysfunctional paths and their
+replacements:
+
+- `/_admin/clusterNodeVersion`: replaced by `/_admin/cluster/nodeVersion`
+- `/_admin/clusterNodeEngine`: replaced by `/_admin/cluster/nodeEngine`
+- `/_admin/clusterNodeStats`: replaced by `/_admin/cluster/nodeStatistics`
+- `/_admin/clusterStatistics`: replaced by `/_admin/cluster/statistics`
+
+Using the replacements will work from ArangoDB 3.7 onwards already, so
+any client applications that still call the old addresses can be adjusted
+to call the new addresses from 3.7 onwards.
+
 ## JavaScript API
diff --git a/3.9/release-notes-upgrading-changes39.md b/3.9/release-notes-upgrading-changes39.md
index 9821515e2c..8360b55ba1 100644
--- a/3.9/release-notes-upgrading-changes39.md
+++ b/3.9/release-notes-upgrading-changes39.md
@@ -93,6 +93,24 @@ in ArangoDB 3.8 and is now removed. If the functionality is still required
 by client applications, running a streaming AQL query can be used as a
 substitution.
 
+#### Redirects removed
+
+Since ArangoDB 3.7, some cluster APIs were made available under different
+paths. The old paths were left in place and simply redirected to the new
+address. These redirects have now been removed in ArangoDB 3.9.
+
+The following list shows the old, now dysfunctional paths and their
+replacements:
+
+- `/_admin/clusterNodeVersion`: replaced by `/_admin/cluster/nodeVersion`
+- `/_admin/clusterNodeEngine`: replaced by `/_admin/cluster/nodeEngine`
+- `/_admin/clusterNodeStats`: replaced by `/_admin/cluster/nodeStatistics`
+- `/_admin/clusterStatistics`: replaced by `/_admin/cluster/statistics`
+
+Using the replacements will work from ArangoDB 3.7 onwards already, so
+any client applications that still call the old addresses can be adjusted
+to call the new addresses from 3.7 onwards.
+
 Client tools
 ------------