Analytics

Add events to existing session replay

post/_temps/session-replay/events

Request

  • Base URL: /api (relative, and the document was published on a file host, not at the API’s origin)
  • URL: /api/_temps/session-replay/events
  • Auth: none declared

Query parameters

temps_keystring

Query-string fallback for the analytics ingest key, for clients that cannot set custom headers (navigator.sendBeacon, used to flush the final replay batch on page unload). Consulted only when the x-temps-analytics-key header is absent; identical precedence and error semantics.

Headers

x-temps-analytics-keystring nullable

Analytics ingest key (ADR-040), pa_ followed by 64 hex characters. An alternative to Host-based project resolution, for apps Temps does not deploy and which therefore have no route-table entry. When present it takes precedence and the Host header is not consulted for resolution; a key that does not resolve to an active row is a 401, never a fallback to Host. The value is public by design — it ships in client JS — and is write-only: it grants analytics ingest for one project (optionally one environment) and nothing else.

Request body

batchIdstring nullable

Client-generated id, stable across retries of the same batch. When present the append is idempotent; omitted, delivery is at-least-once.

eventsstring required
sessionIdstring required

Response

Events added successfully

event_countinteger required
messagestring required

Changes

No recorded changes to this operation across all 50 revisions of this API.