Bring your own data (CSV/JSON import)

Already have historical events — exposures, model calls, conversions — from before you adopted LLMJury? Bulk-import them instead of replaying traffic.

The import endpoint

curl -X POST https://api.llmjury.com/v1/events/import \
  -H "X-API-Key: sk_your_secret_key" \
  -H "Content-Type: application/x-ndjson" \
  --data-binary @events.ndjson

• Secret key only — import is a server-side operation; publishable keys are rejected.
• The body is newline-delimited JSON, one event per line, matching the same event schema as the live SDK path (event_id, type, experiment_id, user_id, variant, timestamp, plus metric fields). CSV works too via the dashboard importer, which maps columns to fields.
• Rows are validated individually: bad rows come back as per-row errors; good rows are ingested.
• Dedup is by client-generated event_id, so re-running an import is safe (idempotent).

Notes

Imported events flow through the same pipeline as live events — judged, rolled up, SRM-checked, FDR-corrected. Timestamps are preserved, so the analysis window reflects when events actually happened; events older than your plan's retention are not analyzable.