List your events
Every event recorded on your account, as a flat array.
This endpoint takes no parameters — there is no filtering, ordering or paging, and anything you send is ignored. Filter on your side, and expect the response to grow with your account.
Authorization
ClientBearer Client-scoped key as a Bearer JWT; always pinned to your own client.
In: header
Response Body
application/json
curl -X GET "https://example.com/tracking/events"{ "data": [ { "id": "evt_9f21", "eventName": "Purchase", "value": 250, "metadata": { "orderId": 182394 }, "createdAt": "2026-07-01T12:00:00.000Z" } ]}Record a conversion POST
Records a conversion — a signup, a purchase, or any event you want to attribute back to a campaign. Two fields are required: an event name, and `coupon` — the Oppizi promo code the conversion came from. Without a valid code the call is rejected, because the code is what ties the event to a campaign. Get yours from [campaign promo codes](/docs/api-reference/campaigns/getcampaigncoupons). See [recommended events](/docs/api-reference/recommended) for the shapes that unlock richer reporting.
Update an event (does not work — do not use) PUT
Do not use this endpoint. It does not update anything. Despite the name and the `PUT` verb, it creates a **new** event, so calling it duplicates the conversion instead of editing it. Recorded events cannot currently be edited. It is documented only so that nobody discovers it in the spec and assumes otherwise.