curl & raw HTTP

Plain HTTP — no SDK required.

You don't need an SDK. Every Millimetric endpoint is a plain HTTPS call with a Bearer token. Useful for shell scripts, GitHub Actions, cron jobs, server backfills, or anything we don't ship a library for yet.

Auth

Authorization: Bearer {key}
Content-Type: application/json

For pk_* keys, also include Origin: matching the project's allowlist (pk_* from servers will fail without it).

Ingest one event

curl -X POST https://api.millimetric.ai/v1/track \
  -H "Authorization: Bearer $SK_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "event": "signup",
    "anonymous_id": "u_abc",
    "user_id": "user_42",
    "properties": { "plan": "free" }
  }'

Expected: 202 {"ok":true,"event_id":null}.

Ingest a batch

curl -X POST https://api.millimetric.ai/v1/batch \
  -H "Authorization: Bearer $SK_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "events": [
      { "event": "$pageview", "anonymous_id": "u_a", "url": "https://yoursite.com/?utm_source=facebook&utm_medium=cpc" },
      { "event": "signup",     "anonymous_id": "u_a", "user_id": "user_1" }
    ]
  }'

Identify

curl -X POST https://api.millimetric.ai/v1/identify \
  -H "Authorization: Bearer $SK_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "anonymous_id": "u_abc",
    "user_id": "user_42",
    "traits": { "email": "[e-mail]", "plan": "pro" }
  }'

Forget a user

curl -X POST https://api.millimetric.ai/v1/forget \
  -H "Authorization: Bearer $SK_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "user_id": "user_42" }'

Query — top sources this month

curl -G "https://api.millimetric.ai/v1/sources" \
  -H "Authorization: Bearer $RK_KEY" \
  --data-urlencode "from=2026-05-01T00:00:00Z" \
  --data-urlencode "to=2026-06-01T00:00:00Z" \
  | jq

Query — daily signups by source

curl -G "https://api.millimetric.ai/v1/stats" \
  -H "Authorization: Bearer $RK_KEY" \
  --data-urlencode "metric=count" \
  --data-urlencode "event=signup" \
  --data-urlencode "from=2026-05-01T00:00:00Z" \
  --data-urlencode "to=2026-06-01T00:00:00Z" \
  --data-urlencode "group_by=source,medium" \
  --data-urlencode "interval=day"

Browser-side (pk_*) — needs Origin

curl -X POST http://localhost:8787/v1/track \
  -H "Authorization: Bearer $PK_KEY" \
  -H "Origin: http://localhost:5173" \
  -H "Content-Type: application/json" \
  -d '{ "event": "$pageview", "anonymous_id": "u_test", "url": "https://yoursite.com/?fbclid=abc" }'

If Origin is missing or not allowlisted you'll get:

403 {"error":"origin_not_allowed","origin":"http://localhost:5173"}

Tips

• Pipe to jq: curl … | jq for legible JSON.

• Save keys to a .env file: export SK_KEY=sk_live_… and source it once per shell.

• Use a fish/zsh function for repeated queries — the URL-encoded query params can get long.

• Logs from the Worker: when something goes wrong, wrangler tail (or pnpm dev:api locally) shows the full traceback. The HTTP response only ever returns a short error code.