Reference · built on requestConnectorAccess control & video

Eagle Eye Cloud VMS

Cameras, bridges, events, and live and recorded media from Eagle Eye Cloud VMS through Video API v3, with webhook subscriptions.

Request accessPricing ↗

About

Eagle Eye Cloud VMS is a cloud video management system from Eagle Eye Networks. Cameras connect through bridges, and an account also holds speakers and displays. Video API v3 exposes cameras, bridges, events, feeds, alerts, notifications, and users at an account-specific base URL, and every feature of your VMS edition is reachable through it. Locations, Floors, and Auditlog need the Professional or Enterprise edition.

Through Fibric, an operator subscribes to motion, person, tamper, and device status events, fetches the image or feed for that moment, and proposes the follow-up. It waits for your approval, sends the request once, and files the receipt.

This is a reference listing. It documents what Fibric would read from Eagle Eye Cloud VMS 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

  • Cameras through GET /cameras with include options such as status, locationSummary, tags, deviceInfo, and firmware, paged at 100 by default
  • Bridges, speakers, and displays as devices, each with connection status
  • Events through GET /events by actor and type, such as een.motionDetectionEvent.v1, een.personDetectionEvent.v1, een.lprPlateReadEvent.v1, and deviceCloudStatusUpdateEvent
  • Event subscriptions through POST /api/v3.0/eventSubscriptions, delivered as server-sent events or webhooks with actor and type filters
  • Feeds through GET /feeds with hlsUrl, rtspUrl, rtspsUrl, multipartUrl, webRtcUrl, and flvUrl for main, preview, or talkdown types
  • Alerts, notifications, and users, and on Professional and Enterprise, locations, floors, and the audit log

Proposed actions

  • Target capability: propose adding a camera through POST /cameras, or renaming and tagging one so it maps to a site or door
  • Target capability: propose a webhook event subscription for a set of cameras and event types, with the technical contact it requires

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

What you can build

  • Know when a camera drops

    deviceCloudStatusUpdateEvent notifications arrive by webhook. The operator waits out your grace period, confirms status through GET /cameras, and proposes a ticket with the bridge and last-seen time.

    With Camera Health

  • Draft the incident with the frame attached

    For a person or tamper detection, the operator pulls the recorded image at that timestamp and the HLS feed link, and drafts an incident record for your approval.

    With Incident Draft

  • Review who was on site after hours

    Motion and person events outside the schedule for each location are listed by camera and time, with image links, for a person to review.

    With After-Hours Audit

  • Match plates to your lot capacity

    een.lprPlateReadEvent.v1 events count arrivals and departures at the entrance camera. When the count nears capacity, the operator proposes the overflow notice.

    With Parking Overflow

Requirements

  • An Eagle Eye developer account with Client Credentials created under My Application; end users never enter these
  • An end-user Eagle Eye Cloud VMS account on the Standard, Professional, or Enterprise edition
  • The account's base URL read from GET https://api.eagleeyenetworks.com/api/v3.0/clientSettings, never hard-coded
  • For webhooks, an HTTPS endpoint that returns 200 OK within 1 second
Authentication
OAuth 2.0 authorization code flow against https://auth.eagleeyenetworks.com/oauth2/token with your client ID and secret and the vms.all scope; refresh tokens renew access without a new login.

Limits

  • Access tokens last at most 12 hours; standard refresh tokens last 90 days and expire after 14 days without use
  • A server-sent events subscription expires after 900 seconds without an event or use; Eagle Eye recommends webhooks for durability
  • Media URLs are generated dynamically and may be cached for at most two hours; the base URL itself can change
  • Camera pages hold at most 500 items; no rate limit figures appear in the reference pages read for this listing

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 Eagle Eye Cloud VMS ↗

Questions and answers

How are events delivered?
Two ways. A subscription with deliveryConfig type serverSentEvents.v1 streams events over an open HTTP connection and expires after 900 seconds of no use. A webhook.v1 subscription posts each event to your webhookUrl and needs a technicalContactEmail and technicalContactName. Filters name the actors and event types.
Which edition does an integration need?
All endpoints are available with the Standard edition, with listed exceptions. Locations, Floors, and Auditlog need Professional or Enterprise. Eagle Eye states that all features available in your VMS edition are available through API v3.
Why is the base URL not fixed?
Accounts sit on regional hosts such as api.c000.eagleeyenetworks.com. After login, GET /api/v3.0/clientSettings returns httpsBaseUrl with the hostname and port for that account. Eagle Eye says not to hard-code it because it is dynamic and might change.
Ask about Eagle Eye Cloud VMS

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 Eagle Eye Cloud VMS 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