Docs / CAMZA.AI
Design for a message arriving twice.
A reliable event receiver needs to consider authentication, temporary failure and duplicate delivery. This guide is an integration checklist, not a statement of Camza delivery guarantees. Establish the actual production signing contract, retry schedule, replay rules and event identifiers before enabling any downstream action with a real-world effect.
UPDATED
Authenticate the sender
Use the mechanism specified by the actual provider contract. Agree credential storage, rotation and how invalid or expired requests are rejected. Signing algorithms and headers must come from a verified API specification.
Handle a duplicate safely
Separate a logical event from individual delivery attempts. A receiver can keep a record of processed event identifiers so that retrying the same notification does not create repeated tickets or actions. Confirm how long that record must be retained.
Test the failure cases
- Receiver timeout before and after processing
- Repeated delivery of the same event
- Invalid credentials and revoked access
- Out-of-order events and delayed recovery
- Rate limits and a permanently unavailable destination
Record the actual guarantees
No Camza signing algorithm, retry interval, delivery guarantee or idempotency window has been published in this release.
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.