How it works
Every guide to camera automation starts by telling you to run something on your LAN and open a port. You don't have to. Cameras have been able to send email since forever, and that outbound connection is all NVR Bridge needs to give you a real webhook.
{
"camera": "Back gate",
"eventType": "VEHICLE_DETECTION",
"plates": [{ "text": "ABC123", "score": 0.91 }],
"channels": [
{ "channel": "01", "images": ["…/optical.jpg"] }
]
}How it works
Each camera you add gets its own private inbound address. That address is how we know which camera an event came from.
Email over SMTP, or upload by SFTP or FTP. Whichever your camera supports — they all end up in the same place.
Method, URL, headers and body, all yours to control. Send the whole event as JSON or shape it for whatever's receiving it.
Events land on a timeline with their snapshots, and every webhook attempt is logged with its status and latency.
What you get
Questions
Both need something on the same network as the camera, running all the time. Email is already outbound and already in the firmware, so there's nothing to host.
There's a round trip to us, so typically a few seconds rather than instant. In exchange there's nothing to maintain and it works from anywhere.
They're stored so the timeline and webhook links work, and removed automatically as they age out. Our privacy policy sets out exactly how long.
Yes, and you should if the footage matters. This runs alongside whatever you already have — it isn't a replacement for a recorder.
Add a camera, point its email at the address we give you, and watch the first event land. About five minutes, all of it in a browser.