Identify Session After Login

PATCH /api/v1/analytics/session/:id/identify — 🔑 Bearer

Sets AnalyticsSession.userId for an existing session. Call this once, right after login or signup completes — the session was created anonymously (likely before the user authenticated), and this pulls the user identity onto it so all the prior pageviews in that session can be attributed correctly.

Request

Path parameters

Headers

No body.

Response

200 OK — ApiResponseOf<IdentifySessionResultDto>

{ "success": true, "data": { "ok": true } }

Errors

The endpoint has no documented 404 or 400 paths — bad session ids and DB failures collapse to a successful response.

Side effects

1. Decode bearer (global JwtAuthGuard); userId = req.user.id.
2. analyticsDb.analyticsSession.update({ where: { id }, data: { userId } }).catch(() => {}). Single SQL UPDATE; failures swallowed.
3. Return { ok: true }.

No throttle on this endpoint. The class registers @UseGuards(ThrottleGuard) but this handler has no @Throttle() decorator and the guard returns true when no decorator is present. In practice clients should call it at most once per session (right after auth completes), so a missing throttle is fine.

Code samples

curl -X PATCH https://api.bio.re/api/v1/analytics/session/ses-uuid/identify \
  -H "Authorization: Bearer $ACCESS_TOKEN"

async function identifySession(
  accessToken: string,
  sessionId: string,
): Promise<void> {
  await fetch(`https://api.bio.re/api/v1/analytics/session/${sessionId}/identify`, {
    method: 'PATCH',
    headers: { Authorization: `Bearer ${accessToken}` },
  }).catch(() => {});
}

// Run this once, immediately after a successful login/signup.
// The session was started anonymously when the page first loaded.
async function onLoginSuccess(accessToken: string) {
  const sessionId = window.__ANALYTICS_SESSION_ID__; // captured from createSession()
  if (!sessionId) return;
  await identifySession(accessToken, sessionId);
  // No need to re-fire; the binding persists for the lifetime of the session.
}

Try it

curl -X PATCH "https://loading/api/v1/analytics/session/string/identify"

{
  "success": true,
  "data": {
    "ok": true
  }
}

{
  "success": false,
  "error": {
    "code": "AUTH_UNAUTHORIZED",
    "message": "Invalid credentials",
    "i18nKey": "auth.login.invalid_credentials",
    "i18nVars": {
      "field": "email"
    },
    "details": [
      {
        "message": "email must be an email"
      }
    ],
    "correlationId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  }
}

Source