Integrating BAS-IP Video Door Entry with Existing Building Systems
At a single site, the property management team may use a dedicated management platform, the security team an access control system, and residents a separate mobile app. When the IP intercom system operates in isolation, the same users, access permissions and events have to be managed in several different places.
BAS-IP can be integrated into the building’s existing digital infrastructure. The property management platform remains the main working interface for staff, while the resident app gains door entry and door release functions.
There are four approaches: interoperability through standard protocols, BAS-IP Link API, BAS-IP Mobile SDK and BAS-IP Device API. Here is when each approach makes sense.
What Is BAS-IP Link?
BAS-IP Link is a software platform for managing connected BAS-IP equipment, sites and flats, users, access credentials, calls and device settings.
It is available in two versions: Link Self-Hosted, installed on the customer’s own server, and Link Cloud, delivered as a BAS-IP cloud service.
Interoperability Through Standard Protocols
Not every integration requires bespoke development. BAS-IP equipment uses standard protocols commonly found in telephony, CCTV and access control systems:
- SIP — an entrance panel registers as a SIP client with the customer’s PBX, allowing calls to reach existing telephones and softphones;
- RTSP — an entrance panel can be added to a video management system (VMS) or network video recorder (NVR) as a video source alongside the site’s other cameras;
- Wiegand — the reader in an entrance panel passes a credential identifier to a third-party access control system.
These scenarios are configured at both ends and do not require integration with a BAS-IP API or SDK.
For SIP integration, check that the audio and video codecs supported by the third-party system are compatible with the specific BAS-IP equipment. For example, BAS-IP supports configurations using PCMA for audio and H.264 for video. The available codecs should be confirmed for each device model and firmware version.
Standard protocols can carry calls, video streams and credential identifiers, but they do not, on their own, synchronise users, flats and access permissions between systems.
Where an organisation needs to automate user management, grant or revoke access permissions, or work with event logs, it can use an API or SDK.
BAS-IP Link API: Integration with Property Management or Back-End Platforms
Link API enables a property management platform, access control system or other existing enterprise platform to automate resident management, access permissions and BAS-IP event handling.
A simple example is a new resident moving in.
A member of staff creates a resident profile in their existing platform, entering the resident’s name, flat and contact details. Without integration, the same person has to be added manually to the door entry system as well.
With Link API, the data is transferred automatically: the resident is created under the correct site and flat in BAS-IP Link, and the information is then applied across the connected BAS-IP infrastructure.
This is just one use case.
Through Link API, a third-party system can work with:
- users and site structure;
- access permissions;
- permanent access credentials, including cards, fobs, access codes, QR codes, Face ID, UKEY and vehicle registration numbers;
- temporary access credentials with a defined validity period;
- guest access and visitor management;
- resident messaging;
- virtual numbers and call forwarding;
- remote device configuration;
- events and logs.
Which functions are used depends on the requirements of the project.
With this approach, the customer’s existing platform can remain the main day-to-day interface for its staff.
Third-party server-to-server integrations using Link API are currently supported for BAS-IP Link Self-Hosted. For projects using Link Cloud, the available integration options should be discussed with BAS-IP.
BAS-IP Mobile SDK: Door Entry Within Your Own App
A second scenario is an organisation that already has a mobile app for residents, tenants or employees.
It may already handle maintenance requests, payments, amenity bookings and notifications. Asking people to install a separate app solely for door entry may be unnecessary.
BAS-IP Mobile SDK allows an existing app to incorporate a broad range of door entry and access control features through BAS-IP Link. Available capabilities include:
- user authentication;
- incoming and outgoing audio and video calls;
- video preview from an entrance panel before answering a call;
- push notifications;
- door release;
- call history;
- BLE-based mobile access through the UKEY component;
- calling a lift to a floor the resident is authorised to access, provided a BAS-IP lift module is installed and configured.
Both iOS and Android are supported.
Residents can answer calls from an entrance panel in the app they already use, view the visitor before answering and release the door.
Developers do not have to build the door entry communication module from scratch. The supplied components already handle SIP communication and interaction with BAS-IP Link, leaving the partner’s team to integrate them into its own app.
Mobile SDK does not reproduce the full functionality of the BAS-IP Link app; it provides a defined set of ready-made capabilities.
Some functions that are not included in Mobile SDK are available through BAS-IP Link API. For example, guest QR code generation and amenity booking can be implemented in the partner’s app through an additional Link API integration.
Third-party mobile app integrations through Mobile SDK are currently supported on BAS-IP Link Self-Hosted.
BAS-IP Device API: Direct Integration with Equipment
BAS-IP Link is not required for every integration.
BAS-IP entrance panels, indoor monitors and other supported devices, including the lift module, have their own local API, allowing a third-party system to communicate directly with the equipment.
The distinction is simple:
Device API connects your system directly to specific BAS-IP devices.
Link API connects your system to BAS-IP Link, which already manages the connected equipment.
Direct integration with devices is suitable for a local project involving a limited, known set of supported device models.
Integration through Link is generally better suited to projects involving different device models, a large number of devices or multiple sites. Link reduces dependence on the specifics of individual models and firmware versions.
Device API is more straightforward to access: its documentation is public and no NDA is required. Simply register on the BAS-IP developer portal at developers.bas-ip.com and confirm your email address.
Webhooks
BAS-IP Android-based entrance panels also support webhooks.
An external system can receive events as they occur, including door release, access granted or denied, device updates and other events recorded in the panel’s log.
This is useful in smart building scenarios where another system needs to respond to an access event or a door being released.
Webhooks are configured directly on the entrance panel through its device settings.
Webhooks are not supported on Linux-based panels, indoor monitors or at BAS-IP Link platform level.
Which Integration Approach Should You Choose?
| What You Already Have | Recommended Approach | Main Objective |
| Telephony, VMS or access control system | SIP, RTSP, Wiegand | Route calls, share video streams or pass credential identifiers without custom software development |
| Property management platform, access control system or other back-end platform | BAS-IP Link API | Integrate resident data, access permissions and BAS-IP workflows with an existing platform |
| Your own mobile application | BAS-IP Mobile SDK | Add door entry calls, video and door release to an existing app |
| Local system using specific BAS-IP devices | BAS-IP Device API | Communicate directly with supported devices and receive webhooks from Android-based panels |
| Back-end platform and your own mobile application | Link API + Mobile SDK | Combine back-end processes with resident-facing functions |
There is no need to choose an approach in advance. The most suitable option usually becomes clear once the existing system and the intended use case have been described.
What Are the Benefits on Site?
- Faster initial setup: user data and related settings can be transferred from the system where they are already managed.
- Less duplicate data entry: staff do not need to enter the same information in multiple interfaces.
- Consolidated site data: door entry and access events can be brought together with other operational information.
- Familiar workflows: staff keep using the systems they know, while residents continue using a single app.
The larger the site, user base and number of connected systems, the more noticeable the benefits.
How Does an Integration Project Work?
The process begins with a discussion of the partner’s requirements. The partner explains which system it uses and what it wants to achieve. For example, residents might need to answer calls from BAS-IP entrance panels within an existing app, or new resident records might need to be transferred automatically from a property management platform. BAS-IP then helps select the most suitable integration method and agree how the finished solution should work.
Once the use case has been agreed, the partner’s team receives the technical materials needed to begin development. An NDA is required for Link API and Mobile SDK, whereas Device API documentation is publicly available. Arrangements for the test environment, licences and equipment are agreed according to the needs of the project.
The partner’s team develops the integration, while BAS-IP specialists provide guidance on their products and help resolve technical questions along the way. If the use case requires functionality BAS-IP does not currently offer, additional development can be discussed. The timescale for such work depends on its scope and the product team’s current priorities.
Once development is complete, the partner tests the integration in its own environment, then demonstrates the result to BAS-IP or provides a description of the implemented solution.
The duration of an integration depends on project complexity, the architecture of the third-party system and the development team’s availability. Setting up the development environment and carrying out tests also affect the timetable.
How Much Does Integration Cost?
By default, BAS-IP does not charge a separate fee for access to integration documentation and tools.
BAS-IP products remain subject to their standard licensing terms, while additional development or changes to development priorities are agreed separately.
Frequently Asked Questions
What Is the Difference Between Link API and Mobile SDK?
Link API connects BAS-IP to a back-end system, such as a property management platform or access control system. Mobile SDK adds door entry functions to an existing mobile app. Both can be used within the same project.
Is BAS-IP Link Required for Integration?
Not always. Many BAS-IP devices have their own local API, so a third-party system can communicate directly with the equipment. Link is generally more useful when an integration covers different models, many devices or multiple sites.
Is an NDA Required?
An NDA is required for Link API and Mobile SDK. Device API documentation is publicly available.
Are Webhooks Supported?
Yes, on Android-based entrance panels. An external system can receive device events in real time. Webhooks are not available on Linux-based panels, indoor monitors or at Link platform level.
Can a Third-Party Platform Be Integrated with BAS-IP Link Cloud?
Third-party server-side integrations through Link API are currently supported on Link Self-Hosted. Equivalent functionality for Link Cloud is in development.
Want to Integrate BAS-IP with Your System?
Tell us which platform, application or equipment you already use, and what you want the integration to achieve.
The BAS-IP team can help identify the right approach: standard protocol interoperability, Link API, Mobile SDK, Device API or a combination of these.