Skip to main content

Session Data

Session Data is the per-session JSON blob — the same shape as Event Data but scoped one level down.

Driven by GET / PATCH /session-data?sessionId=<id> on the API.

Use cases​

  • Session-specific overrides (e.g. wet vs dry tyre rules)
  • Per-session fuel cap / max stint length
  • Stewards' notes per session
  • Reference-lap or reference-setup pointers

How it's modelled​

One row per (accountId, sessionId). Body is a free-form JSON object. PATCH is shallow-merge.

Where the values get used​

  • Math-expression scope — Session.data.<key> resolves into the blob
  • Run plan calculator — keys it knows about (sessionLengthMinutes, etc.) override the session's own fields if present
  • Plugins — when invoked with a sessionId ctx, the host passes Session Data into the call

What you can do today​

  • PATCH per-session keys
  • Read the merged JSON via GET /session-data

What's coming​

  • Inheritance from Event Data → Account Options — keys not present on the session fall through to event, then to account
  • Session Data Definition — declare the canonical keys for a session
  • Reuse last session's data — copy-from-previous helper