SDK Overview

The SDK receives a call from your application and delivers a normalized event to the Trichidata ingestion API.

The SDK receives a call from your application and delivers a normalized event to the Trichidata ingestion API. Everything else — storage, forwarding to destinations, schema discovery — happens on the backend.

How the docs are organized

Page	What it covers
Quickstart	Track your first event end-to-end
Browser / React / React Native / Node	Install and setup for your environment
REST API	Session flow, event schemas, property limits — canonical reference

Choose your SDK

SDK	Install	Status	Docs
Browser	`npm install @trichidata/browser`	✅ Available	Browser SDK
React	`npm install @trichidata/react`	✅ Available	React SDK
React Native	`npm install @trichidata/react-native`	✅ Available	React Native SDK
Node.js	`npm install @trichidata/node`	✅ Available	Node SDK
REST API	—	✅ Available	Reference

All JavaScript SDKs expose the same TrichiDataClient with init, identify, trackEvent, and trackEventsBatch. Start with Quickstart, then open the guide for your platform. Event schemas and HTTP details are in the REST API.

Post-MVP

SDK	Notes
Flutter	—

Getting started

Quickstart — track your first event in under 5 minutes
Browser SDK — vanilla JS and frameworks
React SDK — Provider and hooks
React Native SDK — mobile apps
Node SDK — server-side tracking
REST API — session flow, event types, and request schemas

PII reminder

⚠️ Do not pass personally identifiable information in event properties — no email, name, phone, address, or anything that identifies a real person. Use only an anonymous user_id from your own system. See Compliance.