Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs(security): scope the outbound IP list to Composio Cloud
Self-hosted deployments send requests from their own addresses, so the list does not apply to them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Rayane Boussanni committed
Nov 12, 2026 at 19:32 UTC
5bd3362342f395650a3b438ba29c7cdaa06c7df0
1 file changed
+3
-1
docs/content/docs/security/outbound-ips.mdx
+3
-1
@@ -8,7 +8,7 @@ Some services only accept requests from IP addresses you trust, such as a Salesf
8
9
## IP addresses
10
11
-Composio's requests to connected services, including OAuth authorization, token refreshes, and tool calls, come from these addresses:
11
+In Composio Cloud, requests to connected services, including OAuth authorization, token refreshes, and tool calls, come from these addresses:
12
13
- `52.72.72.59/32`
14
- `54.243.138.89/32`
@@ -17,6 +17,8 @@ Composio's requests to connected services, including OAuth authorization, token
17
18
Add all four. Requests can come from any of them, so a partial list makes connections fail intermittently.
19
20
+A [self-hosted deployment](/docs/security/token-custody) uses its own outbound addresses, not this list. Get them from the team that operates it.
21
+
22
If the service keeps separate allowlists, such as one for access tokens and one for refresh tokens, add all four addresses to each. Some services take each address as its own range, with the same start and end IP.
23
24
## Symptoms of a missing IP