Retrieve a lock or site audit trail using the Salto KS Connect API
domain: developer.saltosystems.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate via OpenID Connect with the Client ID/Secret issued by your Salto Business Unit
Call the Audit resource documented in the Connect API reference, scoped to a specific site
Filter results by date range and, where supported, by Lock or User ID to narrow the audit trail to a single door or person
Cross-reference audit entries against the Locks and Users resources to resolve IDs into human-readable names
Use the Reports resource if a pre-aggregated summary is preferable to raw audit events
Known gotchas
The Connect API reference is generated from an OpenAPI spec that spans dozens of resources (AccessGroups, Entries, Incidents, etc.) — confirm the exact Audit schema live rather than assuming REST conventions from resource naming alone
Non-interactive (server-to-server) integrations use a different OAuth flow than interactive ones — using the wrong integration type during authentication will block audit-trail access entirely
Salto KS and Salto Nebula (a newer platform) have separate developer sections; audit endpoints for one will not work against the other
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?