Skip to main content
When AccessOwl manages a Direct API integration, it makes outbound connections to that application (for example, GitHub) from a fixed set of egress IP addresses. If your team uses an IP allowlist to control which providers can reach your systems, add the addresses below to that allowlist so AccessOwl can keep managing access.

​
Egress IP addresses

Allow both the IPv4 and the IPv6 address. Some integrations connect over IPv6, so allowing only the IPv4 address can leave certain providers unreachable.
If a Direct API integration sits behind an IP allowlist and these addresses are not allowlisted, AccessOwl cannot reach the application and provisioning or revocation requests will result in a reassignment error.

​
These addresses only apply to Direct API integrations

The static addresses above cover Direct API integrations only, such as GitHub, Zoom, and AWS. AccessOwl Agentic Integrations work differently and do not connect from these addresses.

​
FAQ

Yes. AccessOwl runs in Frankfurt, Germany, so the integration account’s sign-ins show up in Germany. Agentic Integrations sign in through a virtual browser the way a person would, for example during a user sync or an offboarding, so some applications and security tools send a sign-in alert for them. These sign-ins don’t come from the static IP addresses above, and the IP address changes between sign-ins.If you restrict where the integration account can sign in from, allow Germany as a location. Don’t disable the integration account or change its password, otherwise Agentic Integrations can’t sign in and their requests and revocations result in a reassignment error.
Last modified on October 14, 2026