Reference · built on requestConnectorAccess control & video

Genetec Security Center

Access, video, and license plate events from Genetec Security Center through its Web SDK, with door, cardholder, and bookmark actions.

Request accessPricing ↗

About

Genetec Security Center is a unified security platform covering access control, video, and license plate recognition. Its Web-based SDK role exposes Security Center methods and objects as web services, so an application can receive and send alarms and events, query access control, video, and license plate events, and check the status of cameras, doors, and applications. SDK documentation, samples, and certificates come through the Development Acceleration Program.

Through Fibric, an operator watches alarm and access events, confirms the door or camera, and proposes a door release, a cardholder or credential change, or a camera bookmark. Nothing runs until you approve it, and the record shows what ran and how to reverse it.

This is a reference listing. It documents what Fibric would read from Genetec Security Center 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

  • Alarms and events from Security Center as they occur, across access control, video, and license plate recognition
  • Historical queries of access control, video, and license plate recognition events, plus license plate reads and hits reports
  • Status of cameras, doors, and applications
  • Cardholders and credentials, readable and modifiable through Web SDK commands
  • Limited PTZ functions on cameras, as the Web SDK documents them

Proposed actions

  • Target capability: propose locking a door, or releasing a locked door
  • Target capability: propose modifying a cardholder or credential, such as an activation or expiry change
  • Target capability: propose adding a bookmark to a camera at the moment of an incident
  • Target capability: propose sending a custom event or alarm into Security Center so monitoring operators see it

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

What you can build

  • Attach video to an access alarm

    A door forced or held alarm arrives from Security Center. The operator checks the door's status, bookmarks the camera covering it, and proposes the alarm for review with the bookmark reference.

    With Door Held Open, Alarm Triage

  • Flag devices that stop reporting

    Status checks on cameras, doors, and applications feed a health list. The operator proposes a work order for each device that stays offline past the window you set.

    With Camera Health

  • Draft an incident from the event trail

    Access, video, and license plate events around a time and place are pulled into one timeline. The operator drafts the incident record for your approval.

    With Incident Draft

  • Expire a contractor's credential on schedule

    When a contractor's end date passes in your records, the operator proposes the credential change in Security Center. You approve; the receipt shows who lost access.

    With Contractor Credentials

Requirements

  • A Security Center system with the Web-based SDK role configured, and a user account holding the privileges the integration needs
  • Membership of the Development Acceleration Program under an SDK agreement, which supplies the SDK package, samples, and a development license
  • A production part number and certificate from DAP@genetec.com; development certificates cannot be deployed on a demo or production system
  • Network reach from Fibric to the server hosting the Web-based SDK role
Authentication
A Security Center user account presented to the Web-based SDK role on each request, plus an SDK certificate whose part number is embedded in the integration; Genetec states token-based authentication is not supported.

Limits

  • The Web SDK has no media library; live and recorded video need the separate Genetec Web Player or another SDK
  • The Web SDK raises no events for door or cardholder assignment changes; Genetec points to the .NET SDK for those
  • Cardholder group membership needs multiple queries; there is no single-call bulk load
  • Full technical documentation sits behind DAP Bronze and Silver tiers, so this listing is written from Genetec's public overview pages

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 Genetec Security Center ↗

Questions and answers

Is the Genetec SDK documentation public?
Partly. Genetec publishes overviews of the Web SDK and the Development Acceleration Program on developer.genetec.com. Full technical content, samples, and certification material need a valid SDK Agreement and Bronze or Silver tier access to the DAP Resource Center.
What does the Web SDK let an application do?
Genetec's overview lists receiving and sending alarms or events, locking and releasing doors, modifying cardholders and credentials, adding bookmarks to cameras, receiving license plate reads and hits, checking the status of cameras, doors, and applications, and querying access control, video, and license plate events. It has many Platform SDK commands but no media library.
How does an integration get licensed?
During development you use the SDK package's development license and certificate. Before deployment, you contact DAP@genetec.com for a production part number and certificate. The certificate string is embedded in the integration and applies only to demo or production systems, not to a development license.
Ask about Genetec Security Center

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 Genetec Security Center 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