> 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.md).

# Schindler

Understand Schindler elevator integration architecture, supported functions, and configuration options.

Gallagher integrates with Schindler elevator systems through cardholder synchronization or access requests. Schindler makes the final elevator-access decision.

Choose one Ethernet method for each deployment. Do not run Call by ID and Call by Profile together.

### Choose an integration method

| Method          | Best for                                        | Requirements                                 |
| --------------- | ----------------------------------------------- | -------------------------------------------- |
| Schindler HLI   | Existing serial deployments                     | Direct Controller 6000 serial connection     |
| Call by ID      | Sites that synchronize cardholder data          | Schindler ID and Badge Numbers               |
| Call by Profile | Sites that send a profile after access approval | REST access and a matching Schindler profile |

Call by ID supports Gallagher readers and Schindler terminals. Call by Profile supports Gallagher readers and does not synchronize cardholder data.

### Configure the integration

* [Configure Schindler ID data synchronization](/knowledge-hub/products/integrations/elevators/schindler/configure-schindler-id-data-synchronization.md)
* [Configure Schindler Call by ID](/knowledge-hub/products/integrations/elevators/schindler/configure-schindler-call-by-id.md)
* [Configure Schindler Call by Profile](/knowledge-hub/products/integrations/elevators/schindler/configure-schindler-call-by-profile.md)

### Diagnose and plan

* [Schindler middleware events do not reach Schindler](/knowledge-hub/products/integrations/elevators/schindler/schindler-middleware-events-do-not-reach-schindler.md)
* [Schindler integration reference](/knowledge-hub/products/integrations/elevators/schindler/schindler-integration-reference-1.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.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.