> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/streaming-integration/faqs/office-ip-whitelisting.md).

# Office IP Whitelisting

When anyone tries to view a stream that is in a geo-blocked territory, our Streaming API will return a 403 forbidden response, and the stream playback URL will not be returned.

However, there are some cases where we consider whitelisting certain IP addresses to override these geo-restriction rules. A good example would be an office for a company that is not within a territory that they hold a license (e.g. Company A has an office in the UK, but they operate in France and their streams are only available in France).

If this applies to you, please email our support team with a whitelisting request and the reasons for the whitelist request (e.g. new office), along with the IP addresses to be whitelisted.

It is also best to let us know if this change will be a permanent or temporary solution. If we determine the range of IP addresses to be too large, we will ask that you consider prioritising your request. We will also take into account any existing whitelisted addresses when reviewing additional requests.

{% hint style="warning" %}
Whitelisting will only resolve issues you have with geo restrictions on streams, this will not resolve any other API authorisation problems. For more details on these and how to resolve them, head to the [Common Authentication/Integration Issues](/streaming-integration/faqs/common-issues.md) section of this documentation. If the answers there do not help resolve your issue, please email our support team.
{% endhint %}

[<br>](https://docs.diceplatform.com/streaming-exchange/-LvkwPA_Ra_7aJsQZbIv/faqs/common-authentication-issues)


---

# 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.sportradar.com/streaming-integration/faqs/office-ip-whitelisting.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.