> 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/api/controller-api-ftcapi-and-middleware-f/controller-api-ftcapi.ini-file.md).

# Controller API - FTCAPI.ini file

Generate and deploy the GallagherFTCAPI.ini file for Controller API communication.

The `GallagherFTCAPI.ini` file applies mainly when Command Centre and the Middleware run on the **same computer**.

## CC 7.80 and later

The ini is **encrypted** and carries the validation information the licence file used to convey, so in most cases the licence file is no longer needed on the middleware machine. Put it there if a customisation will not run.

To generate it:

1. On a Command Centre server or workstation, open **External Systems** and create an External System.
2. Enter the middleware PC's IP address or name. Do **not** use the loopback address `127.0.0.1`.
3. Choose **Import Certificate** and select `GallagherFTCAPI.pem` from the FTCAPI directory, then **Apply**.
4. Choose **Export Configuration** and save `GallagherFTCAPI.ini`.
5. Copy the ini to the middleware machine (where the `.pem` is).
6. Restart `FTCAPIRouterService`.

## CC 7.70 and earlier

All FTCAPI-to-controller comms are hard-coded to **port 1072**. If the middleware is on the Command Centre server, add a **`ListenPort`** registry DWORD at `HKLM\SOFTWARE\CARDAX\Command Centre FT` (or `\Wow6432Node\CARDAX\Command Centre FT`):

1. Stop the Command Centre FT Services.
2. Create the DWORD `ListenPort` (valid range **1024–65535**).
3. Start the services. Controllers go offline.
4. **Push Configuration** to each controller. They come back online after picking up the new configuration.

***

🔗 **Related**

* [Controller API - Server and Middleware](/knowledge-hub/products/cc-software/configure/interface-options/api/controller-api-ftcapi-and-middleware-f/controller-api-server-and-middleware.md). Where the `.pem` and ports come from.
* [Controller API - FTCAPI Error Messages](/knowledge-hub/products/cc-software/configure/interface-options/api/controller-api-ftcapi-and-middleware-f/controller-api-ftcapi-error-messages.md). Errors when the ini or certificate is missing.


---

# 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/api/controller-api-ftcapi-and-middleware-f/controller-api-ftcapi.ini-file.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.