Tracking events

POST /v1/events/track is a public, write-only endpoint built to be called directly from a customer's own website — it can accept events but can't read anything back, so it's safe to call with just a public key, unlike your main API key.

Track a single event

curl -X POST https://api.wezend.com/v1/events/track \
  -H "Content-Type: application/json" \
  -d '{
    "public_key": "pk_live_...",
    "event": "product_viewed",
    "customer_ref": "cus_8823",
    "properties": { "sku": "DK-1180", "price": 499 }
  }'

A single event returns 202 { "ok": true }.

Batch events

{
  "public_key": "pk_live_...",
  "events": [
    { "event": "product_viewed", "customer_ref": "cus_8823", "properties": { "sku": "DK-1180" } },
    { "event": "add_to_cart", "customer_ref": "cus_8823", "properties": { "sku": "DK-1180", "qty": 1 } }
  ]
}

returns 202 { "accepted": 2, "rejected": 0 }.

Origin restriction

You can pass the key as X-ZC-Key instead of in the body. Each public key can optionally be restricted to an allowlist of origins, so a leaked key can only be used to post events from your own domain(s) — an empty allowlist means any origin.

What happens next

Once events land, computed traits recompute and segment membership updates in real time — any journey watching that trigger or segment can fire immediately, no batch job involved.