Bosch video and device integration
Identify the Bosch product and supported integration method. Check media, device control, events and platform functions against the relevant documentation.
Sources and scopeSource record 25 August 2026
Technical source record: 25 August 2026. Check the linked documentation for current product requirements.
Public Bosch Security and Keenfinity catalogue, download, release, and partner material; SDK packages, exact APIs, current version claims, licences, product/build compatibility, and partner only content are excluded.
On this page
Overview#
Vendor APIs / Device and edge video / Bosch and Keenfinity
Bosch Security video integration material is distributed across the Bosch Download Store, product documentation and current Keenfinity integration tools pages. The ownership/branding transition makes source identity and date especially important. Use the current portal linked from the target product and retain the exact package/release letter used for a build.
Documented interface map#
| Surface | Publicly evidenced purpose | Access boundary |
|---|---|---|
| Video SDK | Native video/device integration used by Bosch tools and partner solutions | SDK/version appears in product release artefacts; package, runtime, licence and compatibility require current download/partner material |
| Device/firmware integration support | Device configuration, firmware and plugin support delivered with Bosch tooling | Product and Configuration Manager release letters govern exact support |
| BVMS/integration SDK surfaces | VMS extensions and integrations | Distinct from device Video SDK; verify BVMS edition/build and developer entitlement |
| Integration tools | Access, intrusion, video and partner APIs/SDKs catalogued by Keenfinity | Some packages and high impact command capabilities are partner only or licensed |
| Bosch Security API portal | Public catalogue for selected web service/API initiatives | Individual API maturity and product scope apply; landing text is not an endpoint contract |
Version evidence#
A Bosch Configuration Manager 7.76 release letter dated 15 September 2025 listed Video SDK 6.3 within that release context. This page doesn't claim Video SDK 6.3 is current for every product on 25 August 2026. The proper compatibility unit is the target device firmware, Configuration Manager/BVMS build, SDK package, architecture/runtime and any device support package named by their release notes.
Integration decision#
- Start with a standards based interface such as declared ONVIF support when it satisfies the workflow.
- Select a native device or Video SDK only when the required function and compatibility are explicitly supported.
- Use a BVMS specific extension only for BVMS hosted workflows; don't assume its object model is a general device API.
- Use a web service API only when its official page identifies the target product, maturity, identity flow and lifecycle.
Avoid coupling an integration directly to an internal database, private DLL, browser call or reverse engineered protocol because an official tool happens to use it.
Authentication and privilege#
Obtain the exact current hardening and API/SDK guide. Use TLS with validated device/server identity, unique workload accounts and least privilege. Keep live/playback/export, configuration, firmware, user administration, PTZ/audio and physical output permissions separate where the product allows.
Some Bosch/Keenfinity integration SDKs outside video expose intrusion arm/disarm, silence and output control. Their official data sheets describe them as integration partner and licensed capabilities. This catalogue doesn't transplant those privileges into the Video SDK; it flags why a generic “Bosch SDK account” must never be broadly authorised.
Native SDK handling#
- Verify publisher/signature and package origin.
- Pin architecture, runtime, redistribution and codec dependencies.
- Follow the documented object ownership, threading and callback lifetime rules.
- Bound media buffers, connections, event queues and reconnect work.
- Isolate native SDK failure from the application’s durable event and command state where practical.
- Log package and target build identifiers without recording credentials or media URLs.
- Re test static compatibility on every device firmware, SDK and BVMS/Configuration Manager change.
Lifecycle and support#
Don't interpret a file’s presence in the Download Store as active support. Read its release letter and lifecycle/support statement. During the Bosch to Keenfinity documentation transition, prefer the current link supplied by the target product and note redirects or superseded branding in the project source record.
Primary sources#
- Keenfinity integration tools, current official partner tool catalogue.
- Bosch Security Download Store and firmware catalogue, package and release document route.
- Configuration Manager 7.76 release letter, dated evidence for one tool/Video SDK relationship.
- Bosch Security API portal, official selected API catalogue; inspect each API’s maturity and scope.
- Intrusion Integration SDK data sheet, official evidence of partner/licence and high impact privilege boundaries outside the video scope.