Create a camera key
Open the owned camera’s integration settings, name the integration and choose its expiry. Copy the key once and store it on your server. It can trigger only that camera’s events.
Choose a stable event ID
Use one identifier for the external operation, plus a short name without unnecessary customer or payment data. Duration 0 is a bookmark; 1–3600 requests future capture seconds. There is no pre-roll capture.
Send and retry carefully
POST JSON to /api/v1/integration-events/ with the camera key in the Bearer header. On an uncertain outcome, retry the same ID and identical contents. Changed contents with an existing ID return a conflict.
Verify the result
Find the event in the camera’s workflow events and inspect the timeline. A queued request does not prove a video exists. Existing recording windows are not extended by the event. Test invalid credentials and revocation before using the live business flow.
What success looks like
One external operation appears once and leads to either a bookmark or the observed finite capture outcome.
If it does not work
A disabled camera, missing entitlement or exhausted new-event rate can reject the operation. The limit is 60 new events per camera per minute. Keep the original ID when retrying.
Contact CamBackup support with safe error text, time/timezone and the steps tried. Never send passwords, tokens, OTPs, recovery codes or credential-bearing camera addresses.