Quick Start

Before you begin, make sure you have Geelab console access and have already confirmed the target platform and server-side flow for this integration.

Prerequisites

Access to the Geelab console
A target platform selected: Web, Android, or iOS
A server flow prepared to receive tokens and query the final result

Region Planning

Before integration, review Region Selection so app creation, server configuration, and compliance requirements stay aligned.

Region	Typical Use Case	Recommendation
🌏 Global	Asia-Pacific or globally distributed traffic	Default first choice
🇪🇺 Europe	EU-heavy traffic and GDPR-sensitive scenarios	Use a dedicated app and secret
🇺🇸 North America	North America-heavy traffic	Use a dedicated app and secret

Step 1: Create an app and obtain credentials

Sign in to the Geelab console
Create a new device fingerprint app and select the proper region
Obtain appId
Store the matching private_key on your server

Keep private_key secure. Do not expose it in client code, frontend bundles, or mobile app resources.

Step 2: Finish client SDK integration

Choose the guide that matches your platform:

web-example.js

loadGeelabGuard({
  appId: 'YOUR_APP_ID',
  protocol: 'https://'
})
  .then((instance) => instance.get())
  .then((result) => {
    console.log(result.data.respondedGeeToken || result.data.geeToken);
  });

See the Web Integration Guide for the complete initialization parameters and return structure.

See the Android Integration Guide for SDK initialization, token retrieval, and error-code details.

See the iOS Integration Guide for registration, respondedGeeToken retrieval, and privacy requirements.

Step 3: Submit the token during business requests

After client integration is complete, submit the following to your server during key flows such as registration, login, or checkout:

respondedGeeToken or geeToken
Business context such as request ID, user ID, or order ID
Platform and scenario identifiers

The Geelab device fingerprint server does not currently support querying directly with geeToken.

Step 4: Query the final result on the server

Your server should obtain the queryable gee_token through the device fingerprint service flow, then call fp_query to fetch the final result:

request.json

{
  "gee_token": "server-returned-gee-token",
  "private_key": "YOUR_PRIVATE_KEY",
  "ts": 1712345678
}

Key result fields include:

fp
risk_code
risk_label
client_ip
client_type
access_list

fp_query only accepts the gee_token returned through the device fingerprint service flow. Do not pass the original client token directly into fp_query.

Recommended Order

Finish the client SDK integration
Connect the server-side query flow
Validate both online and fallback token paths
Wire the risk result into allow, step-up verification, rate limiting, review, or reject actions