Sign in

API reference

Sessions

Endpoint POST /api/v1/sessions

Sessions drive adoption and crash-free rates on the Releases page. Send individual sessions or aggregate counts; a session needs a release.

1Request

Public key in X-Blipit-Key or ?key= (for sendBeacon). One session object, {sessions: [...]} with at most 100, or {release, environment?, aggregates: [...]}. A session: sid (8 to 64 letters, digits, dashes), release (required), environment?, status (ok, errored, abnormal, crashed), errors? (a count above 0 means errored), did? (user id, stored only as a hash prefix), started? (ISO or epoch seconds). Sending the same sid again keeps the worst status.

sh
curl "https://in.blipit.io/api/v1/sessions" \
  -H "Content-Type: application/json" -H "X-Blipit-Key: <public key>" \
  -d '{"sessions":[{"sid":"c1f2a9d4e7b8","did":"user-42","status":"crashed","release":"shop@1.4.2","environment":"production"}]}'

2Responses

202 {accepted: n}. 400 when nothing has sid and release, or more than 100 sessions. 401 unknown key.

Good to know

  • 3,000 requests a minute per key.
  • The browser SDK sends these for you with autoSessionTracking: true and a release set; Sentry SDKs' session items are read too.
  • Sessions are kept 90 days.

Stuck? Email support@blipit.io. Keys and the exact DSN for each project are under API keys in app.blipit.io.