Reference · built on requestConnectorAccess control & video

Genea Access Control

Users, cards, doors, locations, access and audit events, and alarms from Genea Access Control, with remote door and emergency actions.

Request accessPricing ↗

About

Genea Access Control is a cloud platform that runs on Mercury and HID VertX hardware. Its v2 REST API at api.sequr.io is organized by customer and location and covers users, tenants, doors, controllers, monitor and control points, schedules, access groups, cards, PINs, badges, visitor logs, alarms, and emergency plans. Webhooks deliver access and audit events to up to five endpoints.

Through Fibric, an operator reads access events and alarms as they post, reconciles cards against your roster, and proposes a door release, a lockdown, a card deactivation, or an emergency plan trigger. You approve, and the record shows what ran and when.

This is a reference listing. It documents what Fibric would read from Genea Access Control 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 /v2/customer/{customer_uuid}/event/access, filterable by door, user, card number, access group, and date range
  • Audit events through GET /v2/customer/{customer_uuid}/event/audit with actor and message filters
  • Alarms through the alarm list and detail endpoints, including Door Contact forced open and held open categories
  • Users with home location, department, status, and custom attributes; user groups and access group assignments
  • Cards and passes, physical and mobile, with lost, found, active, and deactivated states
  • Doors, reader ports, input and output points, controllers, and interface panels per location
  • Attendance, busy-door scans, and hourly heatmaps from the Statistics endpoints; visitor logs from Visitor Management

Proposed actions

  • Target capability: propose a door lock, release, or quick grant through PUT /v2/door/{door_uuid}/lock, /quick_unlock, and the matching release call
  • Target capability: propose a door lockdown or its reset through PUT /v2/door/{door_uuid}/set_lockdown and /reset_lockdown
  • Target capability: propose deactivating, reactivating, or marking a card lost or found through the /v2/customer/{customer_uuid}/card/{card_uuid} actions
  • Target capability: propose suspending or activating a user, or triggering and reverting an emergency plan
  • Target capability: propose acknowledging one alarm or a batch of alarms

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

What you can build

  • Work the alarm queue

    Forced open and held open alarms land as ACCESS events on the webhook and in the alarm list. The operator groups them by door and proposes an acknowledgement with a note once someone has checked the door.

    With Door Held Open, Alarm Triage

  • Keep cards aligned with the roster

    Nightly, the operator compares active cards with your HR system and proposes deactivation for holders who no longer appear, one approval per batch.

    With Badge Hygiene, Access Offboarding

  • Spot access that does not fit

    Access events outside a user's usual hours or at unusual doors are scored against the heatmap baseline. The operator proposes which to review and drafts the question for the site lead.

    With Access Anomaly, After-Hours Audit

Requirements

  • A Genea customer portal and its customer_uuid, which a Global API Key can look up through POST /v2/api_key/verify
  • The location_uuid of each location the operator will read or act on
  • An HTTPS target URL for webhooks; Genea posts from 34.205.175.141 in the US region and 35.158.165.175 in the EU region
  • Webhook payload version 3 when Mercury and VertX hardware are mixed across locations
Authentication
A Global API Key or User API Token from the Genea Portal, sent as Authorization: Bearer {api_token} over HTTPS.

Limits

  • Rate limits are per endpoint per minute: 100 for most endpoints, 60 for List Users, 50 for Create User, 30 for List Building Access event
  • List endpoints require page and page_size, with page_size between 1 and 100
  • At most 5 webhook endpoints per customer; deliveries retry up to 3 times when retry is enabled
  • Webhook signatures use HMAC-SHA1 in the X-Sequr-Signature header, and the payload is application/json only

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 Genea Access Control ↗

Questions and answers

How does Genea authenticate API calls?
With a bearer token in the Authorization header. Global API Keys and User API Tokens are managed in the Genea Portal. With a Global API Key the Me and List my locations endpoints are not available; call Get API Key Detail by API Key to obtain the customer_uuid instead.
How do webhooks work?
Create an endpoint with POST /v2/customer/{customer_uuid}/webhook, giving a name, an HTTPS target_url, status, retry flag, and payload version. Genea POSTs each access and audit event as JSON, signs it with HMAC-SHA1 in X-Sequr-Signature, and expects HTTP 200 quickly. Up to 5 endpoints per customer.
What remote door operations exist?
Lock, a release call, Quick Grant, Set Lockdown, and Reset Lockdown per door, plus location-wide Emergency hold open, hold close, lockdown set, and lockdown reset. Genea documents these for normal doors, conventional elevator doors, and turnstiles.
Ask about Genea Access Control

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 Genea Access Control 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