REST & server API
Server-to-server ingest and analytics with a secret key, plus the dashboard API.
Use the secret key from your backend only. It authenticates with Authorization: Bearer sk_….
Server-side ingest
curl -X POST https://api.your-domain.com/v1/server/events \
-H "Authorization: Bearer sk_…" -H "Content-Type: application/json" \
-d '{"events":[{"event":"subscription_started","user_id":"u_8f3a91",
"consent":{"analytics":true},"properties":{"revenue":7.99,"currency":"USD"}}]}'Read the analytics overview
curl https://api.your-domain.com/v1/server/analytics/overview -H "Authorization: Bearer sk_…"GET /v1/sdk/ping— verify a key (publishable or secret).- Publishable keys can only ingest and read config. Secret keys are rejected in client SDKs (the Unity SDK refuses
sk_keys). - Rate limits apply per key (ingest ≈ 1,200 req/min, config ≈ 2,400 req/min); exceeding returns
429. - Free-tier event allowances are enforced with
402once usage exceeds twice the allowance; paid plans accrue overage instead.
The full machine-readable specification is in the API reference.