Skip to content
Aropath logo
Documentation

Build and Understand Your Business Better On Aropath

Quick starts, API references, and SDKs for every language your team already uses.

Authentication & Key Security

Aropath uses a multi-tiered security model that distinguishes between public client tracking identifiers and secret server-side API keys. This architecture protects workspace administration while enabling client-side analytics collection without risk.

Full Account Authentication Flow

Step 01

Sign Up & OAuth

Register using email/password or authenticate instantly with 1-click Google Sign In.

Step 02

Sign In & Access

Log in anytime with email credentials or Google OAuth to manage projects and team invitations.

Project Key Architecture & Terminology

tracking_key / trackingIdPublic Identifier

Generated upon project creation under Settings → SDK & Tracking → New Project. Displayed ONCE upon creation for security. Used in public HTML script tags (data-id="YOUR_TRACKING_ID"). Safe to expose in frontend client code.

AROPATH_API_KEYSecret Key

Secret API key used for server-side Node.js, Python, and Go SDKs and REST API endpoints (/v1/events/track, /v1/insights, /v1/reports). Must be kept secret in server environment variables and never exposed in client code.

Server-Side SDK Authentication Example

typescript
import { Aropath } from "@aropath/sdk";

// Initialize server-side SDK using your project API key
const aropath = new Aropath({
  apiKey: process.env.AROPATH_API_KEY,
  projectId: "proj_987654321",
});

Key Security & Rotation Protocol

  • Never commit secret API keys to public repositories or client-side JavaScript bundles.
  • Store API keys in environment variables (e.g. .env.local or secret vault).
  • If an API key is accidentally compromised, navigate to Project Settings → API Keys to generate a new key and revoke the compromised credential instantly.

Ready to get started?