developer-friendly BEAT integration.

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.