Gallagher Command Centre integrations
Choose the supported Command Centre interface for the task. Record licensing, product versions and operation permissions before implementing the integration.
Sources and scopeSource record 25 August 2026
Technical source record: 25 August 2026. Check the linked documentation for current product requirements.
Public Gallagher product, integration tool, and Technology Partner material; developer guides, sample code, endpoint contracts, authentication, tokens, API versions, licences, and exact Command Centre compatibility are partner/request gated.
On this page
Overview#
Vendor APIs / Access and identity / Gallagher
Gallagher exposes several separately licensed server and controller interfaces around Command Centre. The public Integration Tools data sheet is the authoritative catalogue level source; detailed developer guides, samples, tokens, demo licences and endorsement workflow are supplied through the Technology Partner programme.
Documented interface map#
| Surface | Publicly documented capability | Access/licence boundary |
|---|---|---|
| REST API View Events & Alarms | Receives selected Command Centre event/alarm information | Server API/licence and partner guide required |
| REST API Create Events & Alarms | Creates external events/alarms in Command Centre | Licensed per server; Cloud API Gateway is offered for remote connectivity |
| REST API Cardholders | Cardholder/credential oriented integration | Exact create/update/delete fields and authority require current guide/licence |
| REST API View Status | Obtains current state for supported Command Centre items | Remote access can use Cloud API Gateway; supported objects/version vary |
| REST API Overrides | Overrides doors, access/alarm/fence zones, macros and outputs | Licensed per server; high impact command surface |
| Cloud API Gateway | Cloud connection to an on premises Command Centre REST API | Subscription/connectivity, identity, tenant and API licence apply |
| Controller API and field interfaces | Controller side integration plus documented ASCII, BACnet, OPC and other interfaces | Distinct trust plane and protocol/licence contract |
| Video Viewer SDK | Embeds third party VMS video in Command Centre UI | Free for development according to product page; licensed per server for deployment |
| Mobile Connect SDK | Embeds Gallagher mobile credentials in iOS/Android applications | Technology Partner access; Cardholder REST API participates in provisioning |
Partner and licence workflow#
Gallagher’s Technology Partner page describes agreement, API selection, portal access, Command Centre environment, development, an integration licensing review, API endpoint inventory, token/demo licence, technical review and endorsement. This isn't an anonymous public API onboarding model. Obtain written confirmation of:
- required REST/SDK/controller interface product codes;
- development and production server licences;
- Command Centre and independently upgradeable REST API versions;
- cloud gateway subscription/region and network route;
- endpoint inventory approved for the integration;
- token/credential lifecycle and partner redistribution terms.
Command Centre v9.10 public material described its REST API as independently upgradeable from the Command Centre server. Treat that as a version specific architecture fact, not proof that every older/current deployment has the same API module or compatibility.
Authentication and authorisation#
Public catalogue pages don't establish the complete current auth contract, so this page doesn't invent one. Follow the partner guide for direct on premises and Cloud API Gateway modes. Use unique integration identities/tokens, validated TLS, network allowlists where appropriate and least privilege by API family and object.
Cardholder synchronisation, event ingestion, status reading and overrides shouldn't share one broad credential. Separate human approval from workload identity and record the Command Centre operator/role, partner token, site and object scope behind every command.
State and event engineering#
- Build an initial snapshot before applying event deltas.
- Persist stable Command Centre identifiers, source/ingest time and event identity.
- Detect server/API upgrade, reconnect, duplicates, gaps and changed object permissions.
- Reconcile cardholders, credentials and object status from authoritative reads.
- Don't equate access granted, door unlocked, door contact open and person passage.
- Bound page sizes, queues, webhook/gateway retries and client concurrency using the gated guide.
For inbound alarms, preserve source provenance and prevent external systems from spoofing native Gallagher events. For status exported to a BMS, minimize personal/security detail.
High impact command boundary#
The Overrides API publicly names doors, zones, macros and outputs and gives lockdown and open door examples. These commands can affect life safety and site response. Require explicit approved use cases, narrow target allowlists, command preconditions, reason codes, dual control where appropriate, and immutable audit. Never blind retry after timeout; reconcile state and operator journal first.
Primary sources#
- Gallagher Integration Tools data sheet, official surface catalogue.
- Technology Partner programme, gated resources, licence/token and endorsement workflow.
- REST API Overrides, supported high impact object classes and per server licence.
- REST API Create Events and Alarms and View Status, event/status and Cloud API Gateway evidence.
- Video Viewer SDK, development/deployment licence distinction.
- Mobile Connect SDK, partner and credential provisioning boundary.