> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cloud-services/cloud-api-gateway.md).

# Cloud API Gateway

Connect remote applications to the Command Centre REST API without inbound firewall rules.

![Cloud API Gateway network architecture: remote and cloud clients reach the gateway over the internet, which tunnels through to the on-premises Command Centre server](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-6c864c6b0b7bcdf49f6a34c6b38e26eb62ab287f%2FSECHUB-cloud-api-gateway-01-architecture.png?alt=media)

The **Cloud API Gateway** lets integrators reach the Command Centre REST API without any on-premises firewall configuration. The customer's Command Centre connects **outbound** to the gateway, and integrators connect **inbound** to the gateway. The gateway tunnels REST API requests through to the on-premises Command Centre server and brokers the calls.

## Why it exists

When the REST API client is on the same corporate network as Command Centre, direct calls work well. Increasingly clients are cloud-based or remote, where direct deployment is difficult and costly. A direct integration often needs corporate IT approval, firewall reconfiguration, and similar work. The Cloud API Gateway removes that.

Conceptually the gateway fills the same role as an HTTP reverse proxy, such as Azure Application Gateway, AWS API Gateway, or HAProxy.

## Direct REST API compared with the Cloud API Gateway

|           | Direct REST API (on-prem)                                                    | Cloud API Gateway                            |
| --------- | ---------------------------------------------------------------------------- | -------------------------------------------- |
| Firewall  | Requires inbound firewall rules to the Command Centre server                 | No customer firewall configuration needed    |
| Best for  | Air-gapped or high-security deployments, lowest latency                      | SaaS-style and remote integrations           |
| Trade-off | Each integration adds firewall rules; network changes can break integrations | Cloud dependency and slight latency overhead |

For a customer asking "can I integrate without opening firewall ports?", the answer is **yes, via the Cloud API Gateway**.

Full setup detail is in the Cloud API Gateway Technical Information Paper on the Gallagher developer documentation site (gallaghersecurity.github.io).


---

# 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://help.security.gallagher.com/knowledge-hub/products/cloud-services/cloud-api-gateway.md?ask=<question>&goal=<user_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.