CamBackup for developers
Build around the moment that matters.
Connect your software to cameras, turn a business event into a recording request, or publish an approved live view. Start with a narrow permission and a test camera.
Developer API, MCP and automation need an active confirmed higher-tier subscription on the account. Widgets require that tier on the shared camera. Normal app use and MFA are available across plans. Compare proposed plans and current availability.
Developer API
Scoped server access to cameras, recorded timelines, clips, jobs and finite event capture.
Start building →MCP tools
Connect a compatible AI client with the same scopes, ownership and plan checks.
Start building →Live camera widgets
Publish a deliberately public view with a revocable CamBackup iframe.
Start building →One permission model
The API, MCP tools and app operate on the same owned resources. A developer credential cannot bypass recording entitlement, current account state, privacy settings or an administrator role check. Separate expiring tokens let you remove one integration without giving it your account password.
The exact request contract
Use the interactive API reference for every supported method, path and body, or download the OpenAPI JSON. The guides explain authentication, safe retries and the difference between requested work and confirmed media.