---
title: "Egress IP addresses"
slug: "api-egress-ip-ranges"
description: "This article serves as an overview for which IP addresses must be whitelisted. "
updated: 2026-08-27T22:27:05Z
published: 2026-08-27T22:27:05Z
canonical: "docs.screenmeet.com/api-egress-ip-ranges"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.screenmeet.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Egress IP Addresses

## Egress IP Addresses

### Overview

This article lists the addresses ScreenMeet calls *from* when it contacts your platform. Add these to your allowlist if you restrict inbound API access by IP address. This applies to any integrated platform, including Salesforce, ServiceNow, Zendesk, and Microsoft Dynamics 365.

Inbound and Outbound Addresses Are DifferentThe addresses on this page are the source of ScreenMeet's calls into your platform. Do not use the addresses listed in [Firewall configuration / whitelisting](https://docs.screenmeet.com/docs/firewall-white-list) for this purpose. Those are destinations that ScreenMeet clients connect to, and they will not satisfy an inbound allowlist.

---

### When You Need These Addresses

- Your platform restricts inbound REST API access to specific source addresses.
- Your ServiceNow instance enforces an IP allowlist through Adaptive Authentication or IP Address Access Control.
- Your Salesforce org restricts API logins by IP range.
- A network appliance in front of your platform filters inbound traffic by source address.

Confirm Your Region FirstScreenMeet calls your platform from the region your organization is provisioned in. Allowlist the address for that region. If you are not certain which region applies, contact ScreenMeet support before applying a rule.

---

### Egress Addresses by Region

| IP | Region | Environment |
| --- | --- | --- |
| `52.199.226.147` | ap-northeast-1 | Prod |
| `18.162.119.69` | ap-east-1 | Prod |
| `18.189.102.45` | us-east-2 | Prod |
| `54.203.112.48` | us-west-2 | Prod |
| `35.175.79.220` | us-east-1 | Prod |
| `13.233.63.88` | ap-south-1 | Prod |
| `18.136.32.15` | ap-southeast-1 | Prod |
| `13.237.249.155` | ap-southeast-2 | Prod |
| `13.209.37.67` | ap-northeast-2 | Prod |
| `18.197.215.150` | eu-central-1 | Prod |
| `18.202.156.6` | eu-west-1 | Prod |
| `18.228.167.44` | sa-east-1 | Prod |
| `3.98.107.181` | ca-central-1 | Prod (Coming soon) |
| `16.170.26.79` | eu-north-1 | Prod (Coming soon) |
| `18.101.72.0` | eu-south-2 | Prod (Coming soon) |
| `51.112.81.246` | me-central-1 | Prod (Coming soon) |

---

### Verification

After adding an address, confirm that inbound calls are reaching your platform:

- **ServiceNow:** Open the **Transaction Log**, filter the **URL** column on `oauth_`, and confirm the `oauth_token.do` entry shows the expected **Remote IP** value.
- **Salesforce:** Review the Login History for the ScreenMeet Service Account user and confirm successful API logins with no authentication failures.

## Related

- [ScreenMeet Enterprise Deployment Guide](/screenmeet-enterprise-deployment-guide.md)
- [Firewall configuration / whitelisting](/firewall-white-list.md)