Genetec Security Center API

Name: Genetec Security Center API
Brand: Genetec Security Center API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecurityThreat DetectionapiKey4 EndpointsREST

For Agents

Read camera inventories, retrieve video streams, query security events, and look up cardholders from a Genetec Security Center deployment.

Install Jentic One Beta

Connect the Genetec Security Center API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Genetec Security Center API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Genetec Security Center API.

List Genetec cameras by site, area, or capability for incident triage

Retrieve live or recorded video stream URLs from a specific camera

Pull security events filtered by time window and event type for SIEM forwarding

GET STARTED

Start building with Genetec Security Center API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Genetec Security Center API, keeping it validated and agent-ready. Genetec Security Center is a unified physical security platform that brings video surveillance, access control, and intrusion events into a single API surface. The spec covers camera inventory, live video stream URLs, security event retrieval, and cardholder lookups so security operations teams can plug Genetec into incident workflows. It targets enterprise sites with mixed Genetec hardware — Omnicast cameras, Synergis door controllers, and AutoVu LPR cameras.

Use Cases

Patterns agents use Genetec Security Center API for, with concrete tasks.

★ SIEM Event Forwarding

Security operations teams running Splunk, Sentinel, or Chronicle need physical-security events alongside their digital telemetry. The Genetec /events endpoint returns timestamped door, alarm, and intrusion events that can be forwarded into a SIEM index, giving SOC analysts a unified view of badge-ins, forced doors, and camera tampering events without standing up a separate console.

Poll /events every 60 seconds, filter for forced-door and tamper events, and forward them as CEF messages to the SIEM

Incident Video Triage

When an alarm fires, a SOC analyst needs the relevant video clip in seconds. Using /cameras to find the camera nearest the event location and /cameras/{cameraId}/video to fetch the stream URL, an automation can attach playback links directly to a ServiceNow or PagerDuty incident before a human opens the ticket.

On a forced-door event, find the nearest camera via /cameras, fetch the video URL via /cameras/{cameraId}/video for the prior 30 seconds, and attach it to the PagerDuty incident

Badge Audit and Access Verification

Compliance and physical-security teams audit who can open which doors. The /access-control/cardholders endpoint exposes cardholder records so an auditor can confirm a specific badge is still active, list cardholders with elevated access, or cross-check badge status against an HRIS termination feed.

For each terminated employee in the HRIS feed, query /access-control/cardholders to verify their badge has been deactivated and report exceptions

AI Agent SOC Co-Pilot

An AI agent acting as a SOC co-pilot can correlate Genetec events with cyber telemetry. Through Jentic the agent searches for 'list security events', loads the /events schema, and executes the call. Credentials remain in the vault and the agent returns a structured event list to the analyst with linked video URLs.

Search Jentic for 'list Genetec security events', load /events, execute it for the last hour, and summarise high-severity events with attached video links

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for genetec security center api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/cameras

List cameras in the deployment

GET

/cameras/{cameraId}/video

Retrieve a video stream URL for a camera

GET

/events

Query security events with time-range filters

GET

/access-control/cardholders

List cardholders and badge details

GET

/cameras

List cameras in the deployment

GET

/cameras/{cameraId}/video

Retrieve a video stream URL for a camera

GET

/events

Query security events with time-range filters

GET

/access-control/cardholders

List cardholders and badge details

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Genetec API keys live in the Jentic vault encrypted with the customer-scoped key. Agents call operations by name and Jentic injects the Authorization header at the edge — the secret never enters the agent's context.

Intent-based discovery

Agents search Jentic by intent ('list Genetec cameras' or 'get security events') and Jentic returns the matching operation with its parameter schema, so the agent calls the correct endpoint without parsing Genetec docs.

Time to first call

Direct Genetec integration: 1-2 weeks for auth, event polling, and video URL handling against an on-prem deployment. Through Jentic: under 1 hour to wire up the four key operations.

FAQs

Specific to using Genetec Security Center API through Jentic.

Why is there no official OpenAPI spec for Genetec Security Center API?

Genetec does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Genetec Security Center API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Genetec Security Center API use?

Genetec uses an API key sent in the Authorization header. Through Jentic the key is stored encrypted in the vault and attached to outgoing requests at execution time, so an agent calling /events or /cameras never sees the raw secret.

Can I retrieve video clips with the Genetec Security Center API?

Yes. Call GET /cameras/{cameraId}/video to receive a stream URL for the specified camera. Combine it with GET /cameras to discover camera IDs by site or area before requesting video.

What are the rate limits for the Genetec Security Center API?

The OpenAPI spec does not declare formal rate limits. Genetec deployments are typically self-hosted, so practical limits depend on the customer's Security Center server capacity rather than a vendor-imposed quota — coordinate with the deployment owner before high-volume polling.

How do I forward Genetec events into a SIEM through Jentic?

Run pip install jentic, search Jentic for 'list Genetec security events', then call /events with a time-window filter. The agent receives structured event objects which can be reformatted to CEF or OCSF and pushed into Splunk, Sentinel, or Chronicle.

Can I look up whether a badge is active?

Yes. GET /access-control/cardholders returns cardholder records including badge status, useful for offboarding audits and termination reconciliation against an HRIS feed.