Integrate the SDK

Geelab provides Web, iOS and Android client SDKs respectively. Please choose the SDK that matches the integration platform and do not mix Public API Keys across platforms.

Choose a platform integration guide

For your first integration, copy the Public API Key from the relevant integration, then follow the platform guide to install and initialize the SDK, configure the Region, and obtain a token. Never pass a Region server key to a client SDK.

For sensitive operations such as login or payment, submit the token together with the business parameters to your backend and retain identifiers needed for correlation. For server-side queries and authentication, see the Server API and Server Integration and Keys.

Integrate the identification results into the business process

After the client SDK obtains a GeeToken, submit it together with the business parameters to your backend. The backend calls the Device Fingerprint API to obtain request_id, device_id, device attributes, and risk signals, then applies risk controls using the relevant account, order, or operation context.

Client SDK identification
   │
   └── GeeToken
          ↓
Customer backend
   │
   ├── Associate the token with the account / order / action
   ├── Query request_id, device_id, and risk signals through the Server API
   └── Decide to allow / challenge / restrict / block

Do not rely solely on self-reported risk results from clients to make high-risk decisions. When it comes to login, transaction or rights issuance, it is recommended that the trusted server query or verify the event results.