Reference · built on requestConnectorAccess control & video

Brivo Access

Users, credentials, access points, sites, and access and audit events from Brivo Access, with door and emergency actions.

Request accessPricing ↗

About

Brivo Access is a cloud access control platform. Its Access API, served from api.brivo.com with an EU variant at api.eu.brivo.com, covers users, credentials, groups, sites, access points, schedules, control panels, cameras, and emergency scenarios. Video is a separate Brivo API built on Eagle Eye Networks.

Through Fibric, an operator reads access and audit events as they arrive on an event subscription, checks device status, and proposes a door release, a user suspension, or a lockdown scenario. You approve. The action runs once and leaves a receipt.

This is a reference listing. It documents what Fibric would read from Brivo Access and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Access events through GET /events/access, filtered by site, object, and event_type such as exception or non_exception
  • Audit events through GET /events/audit by actor, object, schedule, or holiday
  • Users, their credentials, groups, and suspended state through GET /users and GET /users/{userId}/suspended
  • Access points, their cameras, and door state through GET /access-points and GET /device-status/{accessPointId}
  • Sites, groups, schedules, holidays, and control panels with firmware versions
  • Active emergency scenarios through GET /emergency-scenarios/active-scenarios
  • Event subscriptions that POST access or audit events to your URL with an encrypted secret word

Proposed actions

  • Target capability: propose a momentary door release or activation through the POST /access-points/{accessPointId} actions, or a schedule state change through POST /schedules/change-state/{accessPointId}
  • Target capability: propose suspending or reinstating a user through PUT /users/{userId}/suspended, or revoking their credentials
  • Target capability: propose adding or removing a user from a group through PUT and DELETE /groups/{groupId}/users/{userId}
  • Target capability: propose initiating or clearing a lockdown or egress scenario through the emergency-scenarios endpoints

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Flag an after-hours exception

    Exception access events arrive on an event subscription. When a door opens outside its schedule, the operator drafts the incident with actor, access point, and time, and proposes who should see it.

    With Access Anomaly, After-Hours Audit

  • Suspend access on the day someone leaves

    When your identity provider marks a person as departed, the operator finds their Brivo user and proposes PUT /users/{userId}/suspended plus revoke-credentials for your approval.

    With Access Offboarding

  • Watch a door that is being held

    Device status and audit events show a door left open. The operator proposes a notice to the site contact and records whether the door closed.

    With Door Held Open

Requirements

  • A Brivo developer account with sandbox access and an application registered in Brivo Access for a client ID and secret
  • An api-key from the developer portal; calls without it return 403
  • An administrator whose roles cover the sites, users, and access points the operator will read or act on
  • TLS 1.2 or newer on your side; the correct regional host for your account
  • A public HTTPS endpoint if you want event subscriptions pushed rather than polled
Authentication
OAuth 2.0 at auth.brivo.com with authorization_code or password grants and a refresh_token, plus an api-key header from the Brivo developer portal on every API call.

Limits

  • Access tokens expire in 300 seconds by default; the refresh token must be persisted and used
  • An occurred filter on /events/access cannot span more than 24 hours; times truncate to the hour
  • pageSize is capped at 100 with offset paging
  • The Access API documents no per-account rate limit figures; the Video API is a separate product with its own credentials

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Brivo Access ↗

Questions and answers

Does Brivo push events, or do I have to poll?
Both. POST /event-subscriptions registers a URL, criteria such as SITE, USER, or ACCESS-POINT, an errorEmail, and an encryptedSecretWord; Brivo POSTs matching access or audit events to it. GET /events/access and GET /events/audit serve history, one 24-hour occurred window per request.
Can the API open a door?
Yes. The Access_Point tag documents a momentary release action and an activate action on POST /access-points/{accessPointId}, plus activateElevator, and POST /schedules/change-state/{accessPointId} changes the door's schedule state. Each needs an administrator whose role permits it.
Where does video come from?
Brivo's Video API is documented separately at developer.eagleeyenetworks.com and needs its own application. The Access API links cameras to access points through GET /access-points/{accessPointId}/cameras and GET /cameras/{cameraId}/video, and access events can be filtered by the video_linkable type.
Ask about Brivo Access

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Brivo Access through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy