Skip to content
Video analytics · Video analytics API & webhooks

Camera Events in Your Own Systems, as They Happen

Every line crossed, zone joined, queue and occupancy change from CrowdSense Desktop is available over a REST API and webhooks. Feed it into your event app, your screens, your data warehouse or your operations tools.

Webhooks in real time
REST API
Build your own tools
Events, never video
The Problem

The Dashboard Is Fine. Your Systems Need the Data.

A portal is the right place to look at counts. But the event app needs the queue time, the screens need occupancy, the operations log needs the alert and the data team wants everything in the warehouse.

CrowdSense Desktop sends every event to the portal, and the portal hands it on: webhooks push each event as it happens, and the REST API serves history and totals on request.

Capabilities

What You Can Build On

Real-time webhooks

Each event, such as a line crossed or a zone joined, pushed to your endpoint as it happens.

REST API

Query counts, totals and history by camera, rule and period from your own code.

Every event type

Line crossed, zone joined and left, loitering, occupancy, queue length and wait time, and speed.

People and vehicles apart

Each event says what was detected, so people and each vehicle type can be handled separately.

Widgets without code

Embeddable widgets for websites and screens when a live number is all you need.

Many sites, one API

Events from every site and PC arrive through the same portal and the same API.

How It Works

From Camera to Your Code in Four Steps

  1. 01

    Install on a Windows PC

    Download CrowdSense Desktop and install it on a Windows 10, 11 or Server PC on the same network as your cameras, then sign in.

  2. 02

    Add your cameras

    Paste in each camera’s RTSP address, find it over ONVIF, or plug in a webcam. Choose the detection profile that fits each camera: people, vehicles and people, or faces.

  3. 03

    Draw the rules

    Draw the lines and zones that should produce events, and name them so your code can tell them apart.

  4. 04

    Connect your endpoint

    Add a webhook URL in the portal, or call the REST API, and handle events in your own system.

Camera set-up

Where to Put the Camera

Detection profile: whichever fits each camera. Any IP camera that streams over RTSP works, with ONVIF optional, and so does a USB webcam.

Hardware and camera requirements →
  • Any IP camera that streams over RTSP works, and a USB webcam is handy for testing at your desk.

  • Name each line and zone clearly. The name travels with every event and is what your code will filter on.

  • Choose the detection profile per camera: people, vehicles and people, or faces.

  • One feed is one camera stream. Count your feeds before you size the PC: see the hardware guide.

Pricing

Pay per Camera, per Event or per Month

All prices in Australian dollars, excluding GST. One feed is one camera stream.

Event pass

$195

per feed, per event

One event is one primary location, one name and branding, up to 5 days. Feeds go live 14 days before the first day for set-up and testing; dashboards and the post-event report stay readable for 3 months after.

Always-on

From $39

a feed a month, yearly plan

For venues that count every day. Month to month it is $69 a feed for up to 9 feeds, and less at volume. Every band is on the pricing page.

Free trial

14 days

up to 4 feeds

A card is taken at sign-up. Nothing is charged until day 15, and you can cancel any time before then.

No cameras where you need them? For events, we hire Vision Nodes and the crew to install them.Get an events quote.

Download this as a PDF· All brochures and sheets

Who It's For

Who Builds With It

Event app and tech teams

Queue times, occupancy and gate counts inside the event app and on the big screens.

Systems integrators

Camera analytics into access control, signage, PA and building systems.

Data and BI teams

Every event in the warehouse alongside ticketing and sales.

Developers and agencies

Custom dashboards, alerts and experiences on top of live camera counts.

Privacy

Video Stays on Your PC. Only the Numbers Leave.

CrowdSense Desktop analyses the video on the Windows PC it is installed on. What reaches the portal is text: a line was crossed, a zone filled, a queue grew. No video and no images are uploaded, and nothing sent can identify a person.

The software detects people and vehicles so it can count them; it does not identify anyone. No facial recognition, no biometric identification of people. Ever. Your cameras, your recordings and your footage stay on your site, under your control.

FAQ

Video analytics API & webhooks, Answered

Which events are available?

Line crossed, zone joined, zone left, loitering, occupancy, queue length and wait time, and speed, with the camera, the rule and the time of each.

Webhooks or the API?

Use webhooks to react to events as they happen. Use the REST API to pull history and totals when you need them. Most integrations use both.

Is any video or image available over the API?

No. The API and webhooks carry events and counts only. Video stays on your PC.

Can I test without installing cameras?

Yes. Plug in a USB webcam, draw a line on your desk and walk past it.

Try It Free on Your Own Cameras

14 days free on up to 4 feeds. Install on a Windows PC, add a camera, draw a line.

CrowdSense analytics dashboard