Run it on your cameras

Camera intelligence.
For the cameras you already own.

Docs / CAMZA.AI

Make the event contract explicit.

A webhook payload needs enough context for the receiver to recognize an event and decide what to do next. This documentation provides an illustrative event shape for the website demonstration. Camza’s production API contract is not yet confirmed; field names, signing and delivery behavior must be verified before integration work.

UPDATED

Illustrative payload

Example JSON — simulation only
{
  "event_id": "sample-dock-001",
  "mode": "simulation",
  "occurred_at": "2026-09-16T08:30:00Z",
  "camera": {
    "id": "sample-07",
    "label": "Loading dock"
  },
  "event": {
    "label": "person in marked zone",
    "reason": "Sample condition matched"
  },
  "review": {
    "required": true
  }
}

Agree the receiver contract

Fields to discuss
FieldPurposeReview question
Event IDRecognize the logical eventHow are duplicates handled?
Event timePreserve the original event timeWhich timezone and clock source?
CameraIdentify the relevant viewWhich identifiers may leave the site?
ReasonGive the reviewer contextIs the statement observable and useful?
Evidence linkOptional access to a clipWho can open it and when does it expire?

Minimize the transfer

Start with metadata. Add an image or clip only when the use case and access policy require it. Do not include camera credentials or destination secrets in the event body.

A few useful questions.

Can I try this on my own cameras?

Start with a compatibility request. Share camera models, firmware and the event you want to find. An evaluation needs an agreed scope before any camera access is arranged.

Is the website demonstration a product benchmark?

No. The sample demonstration uses illustrative scenes and predefined events. It does not measure accuracy, response time or compatibility on your cameras.

What should we agree before a pilot?

Agree which streams are in scope, who can access the data, where processing runs, retention and deletion, expected outcomes, and the person responsible for reviewing results.

YOUR CAMERAS. YOUR CONTEXT.

Start with one
useful question.

A camera inventory. An event to find.
A clear next step for your team.

Run it on your camerasWhat to bring to a pilot →