Overview

Introduction to SDK

TIKI's SDK is the client-side component that your users will interact with to accept (or decline) data licensing offers.

TIKI's SDK creates immutable, digitally signed license records using cryptographic hashing, forming an audit trail. Programmatically consume records and enforce terms client or server-side using developer-friendly data structures and APIs.

The SDK works across all modern browsers and mobile platforms. Running client-side, with no user data sent to TIKI servers, the SDK requires no changes to your existing backed or data flow(s) to get started.

We offer native, open-source Web, iOS, Android, and Flutter libraries.

👾

Hop over to our Discord if you'd like to propose a port or chat with our team about some of the more experimental work, like Rust.

SDK Flow Overview

The diagram below shows a common flow using the SDK to present the user with a data license offer, which is recorded, signed, and indexed. The resulting license record is available to the client via callbacks and servers through the TIKI API.

Initializing the SDK

Initialization of the SDK requires a Publishing ID. It's free to create one; simply log in to our Developer Console and create a new Project.

Once you have a Publishing ID, pass it to TikiSdk.init() with your app-specific User ID. After that, it's as easy as calling TikiSdk.<method> anywhere in your app. For detailed instructions, see the page for your specific platform: Web, iOS, Android, or Flutter.

TikiSdk.config().initialize('YOUR PUBLISHING ID','YOUR USER ID');

try? TikiSdk.initialize( publishingId: "YOUR PUBLISHING ID", id: "YOUR USER ID")

TikiSdk.init(this, "YOUR PUBLISHING ID", "YOUR USER ID").await()

await TikiSdk.config().initialize("YOUR PUBLISHING ID", "YOUR USER ID")

🌴

Our SDK uses a slick little singleton pattern since you only need a single instance. You can call TikiSdk.<method> while preserving state without passing around and managing objects.