From 3e8103aa98e63b8778558f27908c8581bf90fd25 Mon Sep 17 00:00:00 2001
From: Jason Sooter <7215306+JasonSooter@users.noreply.github.com>
Date: Fri, 15 Aug 2025 12:36:15 -0600
Subject: [PATCH] remove segment api limitation

---
 src/connections/destinations/actions.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md
index 8132257e7c..feccbedfaa 100644
--- a/src/connections/destinations/actions.md
+++ b/src/connections/destinations/actions.md
@@ -32,7 +32,6 @@ Destination Actions are available to all customers on all Segment plans. You do
 - You can use the [Event Tester](/docs/connections/test-connections) with Destination Actions. Event delivery metrics are collected and available in the destination information pages.
 - If you are using [Protocols](/docs/protocols/), Destination Actions actions are applied **after** [schema filters](/docs/protocols/enforce/schema-configuration/) and [transformations](/docs/protocols/transform/). 
 - If you are using [Destination Filters](/docs/connections/destinations/destination-filters/), Actions are applied after the filters. They are not applied to data that is filtered out.
-- Destination Actions can't be accessed or modified using the Segment APIs.
 
 ## Components of a Destination Action