On this page, cookies are needed if you want to use the full range of the page. Please activate cookies and refresh that page. After refresh a cookie management dialogs will be available.

The cookie settings on this website are set to 'allow only strictly necessary' to give you the very best experience. If you continue without changing these settings, you consent to this - but if you want, you can change your settings at any time at the bottom of this page. Our cookie policy


SDKs & protocols


Access to a variety of software development kits (SDKs) and protocols is one of the benefits of registering for the Integration Partner Program.

For full download capabilities, please register as a partner.


Intrusion Integration SDK

  • Integrates Bosch intrusion control panels with third party applications
  • Supports up to 50 control panel connections simultaneously
  • SDK help includes a reference guide with examples
  • Quick connect guide includes code snippets developers can copy and paste to quickly connect their application to Bosch intrusion control panels

The Intrusion Integration SDK (software development kit) facilitates the integration of Bosch intrusion control panels into third party applications.

Developers use the SDK to add functionality to monitor and control Bosch intrusion control panels to their applications.


Monitoring function

Applications can monitor these panel events and conditions:

• Armed state by area, account, or panel (all areas)

• Point state (normal, alarm, trouble)

• Output state

• Primary power (AC, mains) status

• Secondary power (battery) status

• SDI bus device status (keypads and modules)

Controlling function

Applications can execute these functions:

• Arm and disarm by area, account, or panel (all areas)

• Reset detectors

• Test sirens

• Silence alarms

• Activate and deactivate outputs

• Bypass points

• Diagnostic functions


Mode 2 Protocol

Intrusion Integration Protocol (Mode2) Summary

The Bosch B Series and G Series control panels provide an interface to allow external systems to monitor and control the security alarm panel, perform user management, and perform basic maintenance operations.

Commands include:

● Identify panel type

● Authenticate with Panel (this could be and “admin” type user with access to all com-mands or it can be authenticated as a Panel internal user. If authenticated as a Panel in-ternal user the connection will have limited access to commands based on Panel pro-gramming)

● Request Protocol version

● Request Panel Capacities (discover how many Areas, Points, Outputs, Users, Keypads, and Doors are supported by the connected panel)

● Various commands to request whether the currently authenticated user has permission to perform the commands

● Request Panel date and time

● Set Panel date and time

● Request raw history events (control panels have an event log that stores up to 10,000+ events and this command retrieves detailed event data that requires a processing to make it human readable)

● Request text history events (retrieves human readable event data)

● Turn Watch Mode on or off (Watch Mode chimes the keypad when certain entry/exit points are faulted e.g. to indicate a customer is entering a store)

● Reset Sensors (temporarily drops power to select sensors to reset latching alarms)

● Silence (alarm) Bells

● Activate Bell Test

● Send Test Report (to the central monitoring station)

● Display Text At Keypad (temporarily custom text at designated keypad(s))

● Set SKED (scheduled action) Execution Time

● Request current panel status (general overview of multiple panel (global) level status items)

● Multiple commands to identify the current alarm/trouble events and their details

● Request which Areas are currently configured/active

● Request the current arming status of Areas

● Change the current arming status of Areas

● Request a list of Areas not ready to be armed

● Request the status of points

● Request Area Text

● Set Area Text

● Request which Doors are currently configured/active

● Request Door Status (locked/unlocked/blocked)


Mode 1 Protocol

Common Gateway Interface is a standard (RFC 3875) for exchanging data between a BVIP device and a web client. It is applicable for all BVIP devices with firmware 3.0 or higher. Several CGI commands are implemented to control the device simply by using the browser URL. The ability to send RCP commands using CGI enriches the Interface to cover the complete remote protocol feature set and literally configure all settings on BVIP devices.