Sync tenant gate codes and open/verify cloud access points from an external system via storEDGE
domain: api.storedgefms.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate via one-legged OAuth 1.0 with facility-scoped access ID/secret.
Call GET /v1/:facility_id/access_points to list the facility's cloud access points.
Call POST /v1/:facility_id/gate_codes/availability_check before assigning a new code to confirm it isn't already in use.
Update a tenant's code with PATCH /v1/:facility_id/ledgers/:ledger_id/gate_access_code.
Use POST /v1/:facility_id/gate_codes/open to remotely open a gate, and POST /v1/:facility_id/gate_activities to log activity events (e.g., from a third-party panel) back into storEDGE.
Known gotchas
This is storEDGE's own native gate API, separate from any PTI- or Nokē-specific integration — it only works if the facility's gate hardware is wired through storEDGE's own gate-access feature.
gate_activities is a logging endpoint (you POST activity into storEDGE), not a live event stream from the gate; plan for polling or an upstream webhook from the hardware vendor if real-time events are needed.
These endpoints only return data if the facility has the Gate Access Control feature enabled.
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?