> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/workspace/whitelist-firewall.md). # Allowlist Siit on your firewall Whitelist the static IP addresses of the Siit platform and of the third-party integration provider, for EU and US tenants, so webhooks and HRIS or IdP syncs reach you If you're setting up webhooks and running into connectivity issues, your firewall may be blocking Siit's requests. To resolve this, you'll need to whitelist the following static IP addresses. ### Siit platform IPs These are the addresses Siit's own platform uses, for example when sending webhooks to your systems: * `54.76.100.93` * `99.81.157.229` * `3.254.15.174` ### Integration IPs (third-party syncs) Some integrations such as HRIS and identity-provider syncs are handled through our third-party integration provider. Their calls come from that provider's infrastructure, **not** the platform IPs above. If you restrict an integration's API token to only the platform IPs, these calls will be blocked. #### EU tenant * `13.53.228.73` * `13.51.75.140` #### US tenant * `44.194.126.11` * `44.194.4.0` * `3.232.227.174` * `3.214.125.237` * `54.158.121.71` * `44.193.163.62` Add these to your firewall's allowlist to ensure Siit can communicate with your systems without being blocked. If you continue experiencing issues after whitelisting these IPs, feel free to reach out to --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.siit.io/guides/workspace/whitelist-firewall.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.