Trigger a door override command (open/lock) through the Gallagher Command Centre REST API using discovered command links
domain: gallaghersecurity.github.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
GET /api/doors/{id} and read the commands block in the response, which lists discoverable action hrefs such as commands.open.href and commands.lock.href
POST to the discovered href (e.g. the open command href) with an empty body to trigger the override; a successful call returns 204 No Content
Optionally add the requested_by query parameter with a cardholder id so the override is attributed to that cardholder instead of the REST operator
Apply the same discovered-href pattern for overrides on access zones, alarm zones, fence zones, macros and outputs, not just doors
Confirm the RESTOverrides licence and an 'Override - Open Door' privilege are granted to the API key's operator before relying on this in production
Known gotchas
Command hrefs must be discovered per-door from the door resource, not constructed from a fixed URL template — Gallagher's REST API is HATEOAS-driven
Half-cycle door lock commands were only added in server version 9.40 — older servers won't expose commands.lock.href
Missing the RESTOverrides licence or the override privilege returns an authorization error rather than a clear 'not licensed' message
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?