Find an event by what happened.
A refund, a packed delivery or a goods receipt gives your team a reason to review footage. CamBackup lets an application mark the original event time, request the surrounding interval and prepare a private clip when a recording covers it.
Keep your business application focused on its workflow. CamBackup handles the camera recordings and prepares the visual context. You choose the events worth marking.
From a business event to a viewable clip
- Connect one camera. Create an integration key in camera settings and explicitly enable visual evidence access. Keep the key on your application server.
- Mark the moment. Send a stable event ID, an original UTC timestamp and the number of seconds to include before and after it.
- Check availability. Ask CamBackup to prepare the clip. Pending windows, partial or unavailable recordings, failed preparation and ready media have distinct states.
- Review privately. Your server retrieves authenticated MP4 media for the event. No public camera share is needed.
Business context in Vender. Video context in CamBackup.
The Vender integration connects camera sources to business locations and optional tills. Vender records the selected business events and provides an investigation view with separate viewing, exporting and connection-management permissions.
Use a receipt to review a checkout, or a receiving event to examine a delivery. Events need a known physical location. A customer’s shipping address or an inventory default is not automatically a camera location.
Your application can use the same contract
Visual evidence is a general API capability. Connect a warehouse tool, service desk, access workflow or your own business application. The contract has no dependency on Vender order IDs or data models.
{
"external_id": "warehouse:receipt:2026-001",
"event_type": "purchase.received",
"name": "Goods received",
"occurred_at": "2026-10-17T12:30:00Z",
"before_seconds": 30,
"after_seconds": 30,
"retention_days": 7
}Post this shape to /api/v1/evidence/v1/events/ using a camera key with evidence access. Read /api/v1/evidence/v1/capabilities/ first. Use the same external ID and contents when retrying: identical requests return the same event; conflicting contents return HTTP 409.
Call /api/v1/evidence/v1/events/{external_id}/prepare/ to prepare an export and poll the event endpoint. Retrieve /media/ only after the event is ready. The current key is required for every request. Different integration connections cannot read each other’s event references, even on the same camera.
Explicit access. Bounded retention.
Existing trigger-only keys retain their limited permissions. Evidence access must be selected when creating a key. Keys expire, can be revoked and can be rotated without changing their connection identity. Rotation replaces the old secret immediately; security-session changes also invalidate credentials.
Configure event-rate and pending-export limits when creating the key. Each request sets a retention period for its evidence reference and prepared clip. Applications can also send an absolute expiry so delayed delivery never extends it. That period does not extend the retention of the original recordings. Expired references stop serving media, and the cleanup worker removes prepared evidence clips. Event metadata remains in history; expiring a clip does not erase the separate original recording.
Developer integrations require an active confirmed Power or Business subscription. Compare plans or talk with us about your integration.
A bookmark cannot create the past.
The camera must already have recorded the requested interval. Set up recording and check camera clocks before relying on automatic bookmarks. Pre-event footage requires earlier recording; adding an event later cannot recover a recording gap or expired video.
For workflows that need to start future capture, the separate camera trigger API can request a recording window. A successful request is not proof that video was captured. Review the recording timeline and evidence status.
Footage supports human review. It does not automatically establish why something happened or prove misconduct. Share and retain clips according to your organisation’s access policy.