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

# Outbound IP Allowlist

When a VIVI agent connects to an external service — such as a CRM, ticketing system, PMS, or custom API — requests leave our platform from a fixed set of outbound IP addresses. If the system you're integrating with restricts inbound traffic through a firewall, VPN, or access list, you'll need to add these ranges so VIVI can reach it.

Unlike user-facing traffic, which comes from browser or channel endpoints, integration traffic always originates from the ranges listed below.

***

## Outbound IP Ranges

Add the following range to your allowlist. Any request sent from a VIVI agent or integration will originate from one of these addresses.

| CIDR Range           | Last Updated   |
| -------------------- | -------------- |
| `135.237.139.192/28` | April 22, 2026 |

***

## When You Need to Allowlist

You should add VIVI's outbound IPs if:

* Your CRM, helpdesk, or internal API **restricts access by IP**.
* You're connecting VIVI to a service behind a **corporate firewall or VPN**.
* Your webhook endpoint only accepts traffic from **known sources**.

<Note>If your integration lives on a public platform with no IP restrictions, no action is required.</Note>

***

## How to Apply the Allowlist

<Steps>
  <Step title="Locate your firewall or access settings">
    This is usually found under **Security**, **Network**, or **API Access** in the destination system's admin panel.
  </Step>

  <Step title="Add VIVI's outbound IP ranges">
    Enter the CIDR ranges from the table above. Use ranges rather than individual IPs so your integration keeps working as we scale.
  </Step>

  <Step title="Test the integration">
    Trigger the integration from VIVI — for example, run a test conversation or fire a webhook — and confirm the request is accepted.
  </Step>
</Steps>

***

## Best Practices

* Allowlist the **full CIDR range**, not individual IPs, to avoid breakage when our infrastructure scales.
* Subscribe to **release notes** so your network team is notified when ranges change.
* **Re-test your integrations** after any firewall or network change on your side.