Register an app and provision an access credential using the Brivo API
domain: apidocs.brivo.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register at developer.brivo.com and email BrivoAPI@brivo.com to request sandbox access, since production keys aren't self-serve
Create an Application in the Brivo OnAir sandbox account, selecting the Password authentication type for a server-side integration
Exchange credentials for an access token using the OAuth 2.0 flow described in the Access API docs at accessapi.brivo.com
Include both the API key (tied to a permissioned user account) and the access_token in the Authorization header on every request
Create or update a user credential resource to grant that user access to a specific door/group per the Access API reference
Known gotchas
Sandbox access is not instant or self-serve — it requires an email request to Brivo's API team, which can add lead time before any testing can start
Brivo requires both an API key and an OAuth access token on requests; supplying only one produces authentication failures that look like permission errors
Brivo's video product (Eagle Eye Networks) has entirely separate docs and developer portal (developer.eagleeyenetworks.com) — don't conflate its endpoints with the Access API
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?