> 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/cc-software/configure/interface-options.md).

# Interface options

Connect Command Centre through APIs, middleware, protocols, and web services.

Command Centre supports interfaces for exchanging data with external systems and devices. Choose an interface based on the integration's protocol, data flow, and supported platform.

| Interface                                                                                                                                         | Use it for                                                                                  |
| ------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| [APIs and middleware](/knowledge-hub/products/cc-software/configure/interface-options/api.md)                                                     | Connect applications through REST, controller APIs, ASCII interfaces, or middleware plugins |
| [Enterprise data interface (EDI)](/knowledge-hub/products/cc-software/configure/interface-options/enterprise-data-interface-edi.md)               | Synchronize cardholder data with external data sources                                      |
| [Facility management interfaces](/knowledge-hub/products/cc-software/configure/interface-options/facility-management-interfaces.md)               | Connect building systems, booking platforms, and Command Centre servers                     |
| [OLE for process control (OPC)](/knowledge-hub/products/cc-software/configure/interface-options/ole-for-process-control-opc.md)                   | Support legacy OPC Data Access and Alarm and Event integrations                             |
| [Open supervised device protocol (OSDP)](/knowledge-hub/products/cc-software/configure/interface-options/open-supervised-device-protocol-osdp.md) | Connect supported OSDP devices to Command Centre                                            |
| [Session initiation protocol (SIP)](/knowledge-hub/products/cc-software/configure/interface-options/session-initiation-protocol-sip.md)           | Connect supported SIP intercom devices with Command Centre Client                           |
| [Software development kits (SDKs)](/knowledge-hub/products/cc-software/configure/interface-options/software-development-kits-sdks.md)             | Extend mobile access and video viewing applications                                         |
| [Web services](/knowledge-hub/products/cc-software/configure/interface-options/web-services.md)                                                   | Support legacy SOAP integrations for cardholder and visitor management                      |


---

# 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/cc-software/configure/interface-options.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.