ttlock app localized docking solution
Back to the new list

TTLock API on-premiseAbstract

TTLock API on-premise is for third party software developers who want to maintain all lock related data on their own server, and want to generate passcode and issue ekey from their own server. With this on premise solution, they don't need to call API from TTLock server.




Who are these API for

1. Developers from countries where data are required to be stored in their own country

2. Big software systems or platforms who require to maintain all their data on their own server, like airbnb, booking.com

3. Schools, government departments




What are included

1. jar package：It is deployed on server to generate passcodes or ekeys

2 Android and iOS native SDK：They are for native developers to communicate with locks via bluetooth.

3 Flutter SDK：It is for Flutter developers to communicate with locks via bluetooth

4 React Native SDK：It is for react native developers to communicate with locks via Bluetooth

5 Gateway server: Communicate with gateways

The jar package is a must. You should put it on your own server. Then select one of the other three SDKs depending on which platform you are working on.




What is the process of integrating

Take native app development for example.

1 Call android/ios SDK to initialize a lock. The SDK will return lockdata to you.

2 Save this lockdata on your own server

3 To generate a passcode, call jar api and pass in lockdata as parameter. The jar api will return the passcode to you.




Tips: Some SDK functions will change lockdata, please replace current lockdata with the new one on your server.




What is the price

You should pay for the API on-premise.

To test the SDK, please set the bundle ID to com.justfor.test