Skip to main content

Event Data

Event Data is the per-event JSON blob — a place to stash constants and overrides that apply to one event without polluting the wider account.

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

Use cases​

  • Track-specific corrections (e.g. a Sebring-only ConcreteFactor that the math engine multiplies into tyre pressure recommendations)
  • Per-event tyre-allocation rules
  • Per-event fuel-density overrides
  • Notes the event director needs every car to see

How it's modelled​

One row per (accountId, eventId). Body is a JSON object with whatever keys make sense. PATCH is shallow-merge — only the keys you send are updated.

Where the values get used​

  • Math-expression scope — Event.data.<key> resolves into the blob
  • Run plan calculator — keys it knows about (e.g. fuelDensityKgPerL) override the default
  • Plugins — when invoked with an eventId ctx, the host passes Event Data into the call

What you can do today​

  • PATCH per-event keys
  • Read the merged JSON from any client via GET /event-data

What's coming​

  • Inheritance from Account Options — keys not present on the event fall through to the account default automatically (today the consumer has to ask both)
  • Defaults from Definition — let a Definition declare default keys with types (mirrors HH-DM's "EventData definition")
  • Inline editor with type hints