developer-friendly BEAT integration.
Discover the potential of BEAT integration with developer-friendly documentation.
Learn how to manage your ABLOY BEAT locking devices, users and operating devices, and grant access to keyless opening with the practical request and response samples.
How to integrate ABLOY BEAT
- Access our Partners Portal to create a record for your integration.
- Get direct access to the Support team and restricted documentation
BEAT integration process from start to finish
Administration API
Manage your ABLOY BEAT locking devices and users via the BEAT integration interface. See how to invite Operating devices, add locking devices, and grant access to keyless opening with the practical request and response samples.
Do you have questions?
ALCEA’s sector specialists will help you figure out the right solution for you. Leave a message and we will contact you soon.
Explore the available solutions with your local partner or with your ALCEA representative. Check out our distribution map for more information or leave us a message.
FAQ BEAT API
BEAT API provides an interface to manage access for ABLOY BEAT locks through a 3rd party system.
BEAT API is targeted for system integrators capable of handling users, access permissions, and locking points geographically. The end-user of the ABLOY BEAT locks may be the integrating company or a client of the integrator.
The integrating interface sends requests to the BEAT API and receives responses from it. The REST API determines the rules for the parties to use a common method of communication. With the REST commands it is possible to, e.g., invite new BEAT users, add locks and provide open permissions to the users.
Yes, the callbacks interface can be subscribed to receive the events of a specific tenant through a Northbound Interface.
In this case, CIPE Manager can still be used for access management.
No. BEAT API is only available for access management integration at the moment and requires the BEAT Mobile Application as a part of the solution.
A mobile SDK (software development kit) will be available for customized application development at a later stage.
Not at the moment. There is no synchronization between BEAT API and CIPE Manager. However, an alarm interface with a subscription (read only) can be combined with CIPE Manager management.
Not at the moment. BEAT API uses REST whereas the CLIQ integration uses SOAP.
Please use the form at the end of this page and include all the possible information you wish to provide. We will contact you as soon as possible.
FAQ BEAT SDK
BEAT SDK provides a set of libraries to be used for the development of an Android or iOS application. It provides the tools to operate BEAT devices such as for register users and devices, to open a lock or store audit trails in the BEAT device.
BEAT SDK is targeted for Android and iOS application developers who are willing to implement the functionality to operate BEAT devices.
The library enables communication with BEAT devices through the Bluetooth connectivity of a mobile device. It also takes care of communication to the BEAT API for specific actions such as to register a user or device and upload audit trails from the BEAT device.
No. BEAT SDK is only designed to operate the BEAT devices and invitations for BEAT users. In order to implement access management functionalities for BEAT, the use of BEAT API is required.
Several apps that implement the mobile BEAT SDK can coexist in the same device. However, each registered app is handled as an independent user in the BEAT backend.
Yes. It can. For example, one customized mobile app could implement both BEAT SDK and ASSA ABLOY CLIQ Connect SDK to control both ABLOY BEAT devices and ASSA ABLOY CLIQ devices.
Please use the form at the end of this page and include all the possible information you wish to provide. We will contact you as soon as possible.