Skip to main content

Available SDKs

Android (Kotlin)

Native SDK — Kotlin detectors plus a native C layer (JNI) for the unhookable root/debugger checks. Requires NDK + CMake to build.

iOS (Swift)

Native SDK — Swift detectors using Darwin-level APIs (sysctl, Secure Enclave, getifaddrs) for the same detection categories as Android, with documented platform-parity differences.

Flutter

A single Flutter plugin wrapping both native SDKs, with scoring and telemetry logic shared in Dart so both platforms score identically by construction.

Web (JavaScript)

Browser-based fingerprinting and behavioral telemetry for web checkout/login flows — see Beyond RASP.

Getting your credentials

Every integration starts with a tenant, created from the DI Dashboard:
1

Request access

Contact akash@insightai.in or your InsightAI account contact for dashboard access.
2

Create a tenant

From Admin → Integrations, create a tenant for your app. This generates three credentials, shown once:
  • A public API key (dpk_live_... / dpk_sandbox_...) — identifies your tenant on dashboard-facing calls
  • A private HMAC secret — signs every telemetry payload the SDK sends; never exposed client-side beyond the SDK’s own config
  • A webhook signing secret — verifies payloads InsightAI sends back to you
3

Configure the SDK

Pass the HMAC secret into the SDK’s config at app startup — see the platform-specific snippets below.
4

Verify with a test evaluation

Run one evaluation and confirm it appears in the DI Dashboard’s live telemetry feed before going further.
The private HMAC secret and webhook signing secret are shown once, at creation time. Store them in your secrets manager immediately — they can’t be retrieved again, only rotated.

Quick integration

Next steps

API Authentication

Full detail on key types, HMAC signing, and rotation.

Webhooks & Payload Reference

Every field in the telemetry and alert payloads, explained.