# Provide an endpoint to retrieve Auth0 egress public IP addresses

**URL:** <https://community.auth0.com/t/provide-an-endpoint-to-retrieve-auth0-egress-public-ip-addresses/86294>\
**Category:** Get Help\
**Created:** [July 1, 2022, 8:07pm UTC](https://community.auth0.com/t/provide-an-endpoint-to-retrieve-auth0-egress-public-ip-addresses/86294 "2022-07-01T20:07:11Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![romain.aviolat](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/romain.aviolat/32/13366_2.png) [@romain.aviolat](https://community.auth0.com/u/romain.aviolat)\
**Post date:** [July 1, 2022, 8:07pm UTC](https://community.auth0.com/t/provide-an-endpoint-to-retrieve-auth0-egress-public-ip-addresses/86294/1 "2022-07-01T20:07:11Z")

</div>

Currently Auth0 provides its egress IP addresses in a human-readable format only inside the following documentation → [Auth0 IP Addresses for Allow Lists](https://auth0.com/docs/secure/security-guidance/data-security/allowlist).

For clients filtering Auth0 ingress traffic (logs or webhooks) the only way to do it today is to manually parse the info on that page. This is error prone and inefficient, especially when new IPs are added it’s difficult to monitor changes and the teams can miss the Auth0 notifications.

That’d be nice if Auth0 could provide a machine-friendly endpoint that could be queried by scripts or automation, especially for teams working with Infrastructure-as-Code.

As an example this is how Cloudflare implements it (human-friendly doc + REST API + static file) [IP Ranges](https://www.cloudflare.com/ips/)

---

<div class="post-metadata">

**Author:** ![rmgarrett94](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rmgarrett94/32/45197_2.png) [@rmgarrett94](https://community.auth0.com/u/rmgarrett94)\
**Post date:** [March 7, 2023, 5:25pm UTC](https://community.auth0.com/t/provide-an-endpoint-to-retrieve-auth0-egress-public-ip-addresses/86294/2 "2023-03-07T17:25:56Z")

</div>

+1 This would be useful.

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [March 8, 2023, 9:16am UTC](https://community.auth0.com/t/provide-an-endpoint-to-retrieve-auth0-egress-public-ip-addresses/86294/3 "2023-03-08T09:16:09Z")

</div>

Hey there Guys!

Can anyone of you create a Feedback card regarding that in our Feedback category here so it can start getting traction from other community users as well? Thank you!

> **[Feedback](https://community.auth0.com/c/feedback/95)**
>
> Submit and vote on product feedback and feature requests.

---

<div class="post-metadata">

**Author:** ![jgraham](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jgraham/32/58975_2.png) [@jgraham](https://community.auth0.com/u/jgraham)\
**Post date:** [August 1, 2024, 4:01pm UTC](https://community.auth0.com/t/provide-an-endpoint-to-retrieve-auth0-egress-public-ip-addresses/86294/4 "2024-08-01T16:01:06Z")

</div>

+1 here. This should be base level for any service that publishes egress IPs – provide a machine readable JSON or flat text version so we can easily consume it in automation.

---

<div class="post-metadata">

**Author:** ![hamza.mhirsi](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/hamza.mhirsi/32/60021_2.png) [@hamza.mhirsi](https://community.auth0.com/u/hamza.mhirsi)\
**Post date:** [September 6, 2024, 8:19am UTC](https://community.auth0.com/t/provide-an-endpoint-to-retrieve-auth0-egress-public-ip-addresses/86294/5 "2024-09-06T08:19:41Z")

</div>

- 1 here. This will allow having an updated list without the need of reviewing those IPs manually.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [December 5, 2024, 11:19pm UTC](https://community.auth0.com/t/provide-an-endpoint-to-retrieve-auth0-egress-public-ip-addresses/86294/6 "2024-12-05T23:19:36Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![ale.vesga1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ale.vesga1/32/60921_2.png) [@ale.vesga1](https://community.auth0.com/u/ale.vesga1)\
**Post date:** [December 6, 2024, 12:16am UTC](https://community.auth0.com/t/provide-an-endpoint-to-retrieve-auth0-egress-public-ip-addresses/86294/7 "2024-12-06T00:16:52Z")

</div>

Vote and Comment here for traction:

> [@Endpoint to retrieve Auth0 egress public IP addresses](https://community.auth0.com/t/endpoint-to-retrieve-auth0-egress-public-ip-addresses/157791):
>
> Currently Auth0 provides its egress IP addresses in a human-readable format only inside the following documentation → [Auth0 IP Addresses for Allow Lists](https://auth0.com/docs/secure/security-guidance/data-security/allowlist). For clients filtering Auth0 ingress traffic (logs or webhooks) the only way to do it today is to manually parse the info on that page. This is error prone and inefficient, especially when new IPs are added it’s difficult to monitor changes and the teams can miss the Auth0 notifications. That’d be nice if Auth0 could provide a machine-friendly…
