Server SDK

Server-side tracking via the Growise Events HTTP API. Use when you need trusted backend events (purchases, subscriptions) that browsers or apps should not forge.

Overview

Send events from your backend with your project API key. Prefer server events for billing-critical actions; keep the key only on the server.

Authenticate with project API key (gk_…)
POST batched events to your environment events base /track
Include user_id when known; otherwise anonymous / guest ids from prior identify flows

Event bases by environment

Use the Events base URL from your Growise project / dashboard settings
Production: https://events.thegrowise.com
Never embed real API keys in client apps or public docs

Track example (cURL)

POST /trackbash

curl -X POST 'https://events.thegrowise.com/track' \
  -H 'Content-Type: application/json' \
  -d '{
    "api_key": "gk_your_key",
    "user_id": "usr_99812",
    "event": "Purchase Completed",
    "properties": { "amount": 99, "currency": "INR" },
    "timestamp": "2026-08-24T05:00:00.000Z"
  }'

Best practices

Keep API keys in server secrets — never in mobile or web bundles for privileged writes
Idempotency keys for purchase events when your pipeline retries
Align event names with client taxonomy (past tense, stable keys)