Authenticate to the Feenics (Keep by ACRE) access control API and call a basic resource endpoint
domain: apidocs.acresecurity.cloud · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST to https://api.us.acresecurity.cloud/token with grant_type=password, client_id, client_secret, username (format instance_name\username), and password to obtain an access token
Use grant_type=refresh_token against the same token endpoint to refresh without re-sending the password
Call resource paths of the form https://api.us.acresecurity.cloud/api/f/INSTANCE.KEY/[resource] and /[resource]/[RESOURCE.KEY] for GET/POST/DELETE, sending Authorization: Bearer {access_token} on every call
Work with the documented object model (UserInfo, BuildingInfo, FloorplanInfo, FolderInfo, InputScannerInfo, AcreIntrusionCalendarInfo) and door 'Service Commands' for actions
Prefer the maintained C#/.NET client library if you're on that stack; for other languages, call the REST endpoints directly per the acresecurity.cloud reference
Known gotchas
The username field requires an instance-qualified format (instance_name\username), not just a bare username — a common source of 401s
The product has rebranded from Feenics to 'Keep' under ACRE, and docs now live at apidocs.acresecurity.cloud rather than the legacy apidocs.feenics.com — check you're on the current host
Non-.NET integrations have to hand-construct the instance-key-qualified resource paths since the primary supported path is the .NET wrapper library
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?