> 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/integrations/elevators/schindler/schindler-integration-reference-1.md).

# Schindler integration reference

Reference Schindler integration versions, architecture, ports, plugins, credentials, and hardware requirements.

Use this reference to plan a Schindler integration and verify its technical requirements.

### Integration methods

| Method                         | Introduced                 | Relationship                                         |
| ------------------------------ | -------------------------- | ---------------------------------------------------- |
| Schindler HLI (Miconic Serial) | Before Command Centre 7.00 | Direct Controller 6000 serial connection             |
| Schindler ID and Call by ID    | Command Centre 7.00        | Call by ID uses synchronized cardholder data         |
| Schindler Call by Profile      | Command Centre 8.10        | Standalone method without cardholder synchronization |

Call by ID and Call by Profile are not designed to run together.

### Architecture

Ethernet integrations use a Middleware PC running the Gallagher FTCAPI Middleware Framework. The vendor baseline is Schindler ID version `1.3.369.1`.

| Path                                | Port            | Purpose                          |
| ----------------------------------- | --------------- | -------------------------------- |
| Command Centre Server to controller | 1072 by default | Controller communication         |
| Schindler ID to Schindler Server    | TCP 4040        | Cardholder synchronization       |
| Middleware to Schindler             | TCP 5050        | Reader access and floor override |
| Schindler to Middleware             | TCP 6060        | Events and floor-state changes   |

### Plugins

| Plugin                 | Call by ID             | Call by Profile | Purpose                                          |
| ---------------------- | ---------------------- | --------------- | ------------------------------------------------ |
| Call Manager Interface | Gallagher readers only | Required        | Sends reader access requests and floor overrides |
| Life/Live Reporting    | Optional               | Optional        | Receives Schindler decisions and events          |

### Credentials and terminal hardware

Schindler ID supports 26/8-bit, 35/12-bit, 37/16-bit, and 48/22-bit Wiegand formats. It also supports Gallagher-encoded DESFire cards.

Schindler terminals need a SAN/SAM card for Gallagher-encoded MIFARE Classic and DESFire cards. The card uses the site's MIFARE Site Key. Default keys do not support DESFire.

Gallagher Professional Services encodes SAN/SAM cards as a paid service. Request one through your Gallagher account contact.

### Related information

* [Elevator integration interfaces and limits](/knowledge-hub/products/integrations/elevators/hli-reference.md)
* [Elevator integration glossary](/knowledge-hub/products/integrations/elevators/glossary.md)


---

# 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/integrations/elevators/schindler/schindler-integration-reference-1.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.