> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/technical/network-access.md).

# Network access

Flow Retail runs 100% online, in the cloud, always available wherever you have internet access, and in most scenarios you will not need to configure anything special to get access.

Some networks has outbound restrictions, and in this article you will find details on what needs to be opened outbound to be able to use Flow Retail.

## Domains and IP Addresses

To be able to use the Flow Retail your network needs to be set up to access certain domains and IP addresses. If your firewall is blocking outgoing traffic you need to open for these IP addresses and domains.

### Flow Retail

#### API and Services

<table><thead><tr><th width="328">Domain</th><th width="170">IP Address</th><th width="96">Ports</th><th>Protocols</th></tr></thead><tbody><tr><td>api.flowretail.com</td><td>185.49.4.60</td><td>443</td><td>https</td></tr><tr><td>mq.flowretail.com</td><td>185.49.5.210</td><td>5671</td><td>amqps</td></tr><tr><td>backoffice.flowretail.com</td><td>185.49.4.65</td><td>443</td><td>https</td></tr><tr><td>-</td><td>185.49.4.78</td><td>8140</td><td>https/puppet</td></tr></tbody></table>

#### Webhooks

This is a list of all IP addresses where webhook notifications may come from:

```
185.49.4.25
```

### 3rd Party Systems

#### Nets Payment Terminal - Cloud Connect

To use Nets Connect\@Cloud, the firewall needs to allow traffic to these IP addresses:

| IP Address     | Ports        |
| -------------- | ------------ |
| 3.33.230.243   | 6001 and 443 |
| 15.197.206.182 | 6001 and 443 |

#### Stripe

Follow the [Stripe instructions](https://docs.stripe.com/ips)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flowretail.com/docs/technical/network-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.