canonical: https://jentic.com/apis/genetec.com/genetec # Genetec Security Center API 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. ## For AI agents Read camera inventories, retrieve video streams, query security events, and look up cardholders from a Genetec Security Center deployment. ## Scope Does not handle cybersecurity threat detection, endpoint protection, or network firewall rules - use for physical security event, video, and cardholder operations only. ## Capabilities - 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 - Look up cardholder records to confirm whether a badge is active and authorised - Build cross-system incident playbooks by joining camera, event, and cardholder data ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Cameras** — List cameras and retrieve live or recorded video streams - **Events** — Query security events including alarms, intrusions, and door activity - **Access Control** — Look up cardholder records and badge status ## Why Jentic - **Setup:** Wiring the Genetec Security Center API by hand means setting up its Authorization-header API key and routing camera, video, event, and cardholder calls to the right paths yourself. Through Jentic you install once, import Genetec from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Genetec puts the camera id in the URL path (`/cameras/{cameraId}/video`), so a rule can pin your agent to one camera: it can read that camera's video and nothing else. You choose the operations it may call, so broader ones like listing all events or reading access-control cardholders are not included unless you add them. - **Credential handling:** Your Genetec API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list Genetec cameras' or 'get recent security events', and Jentic returns the matching operation with its parameter schema so the agent calls the correct endpoint without parsing the reference docs. ## Related APIs - **Verkada** — Cloud-native physical security platform with cameras, access control, and environmental sensors - **Twilio** — Send SMS or voice alerts when Genetec emits a high-severity security event - **OpenALPR** — Cloud licence-plate recognition for vehicles entering monitored sites ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the Genetec Security Center API? Yes. Because you self-host Jentic One, your own rules decide which of the four Genetec operations the agent may call and which credentials it may use. Since the camera ID sits in the URL path (GET `/cameras/{cameraId}/video`), you can pin the agent to a single camera's video and nothing else, and you choose whether it can also list cameras via GET /cameras, query GET /events, or read GET `/access-control/cardholders.` Broader operations like listing all security events or reading cardholder records are excluded unless you explicitly grant them.