Strategic Nice-to-Haves — Launch Monitor & Session Partners

These are not required for launch, but would meaningfully improve the integration quality and user experience.

Bulk Historical Export

Provide a batch endpoint (e.g., GET /sessions/export?startDate=&endDate=) that returns all sessions in a date range in a single paginated response. This accelerates first-time user onboarding when we need to backfill months of history.

Incremental Sync Support

Expose a ?modifiedSince= filter on your session list endpoint so we can poll for only newly created or updated sessions since the last sync. Useful as a fallback for partners that cannot support webhooks, or as a lightweight daily consistency check.

Target / Drill Context

If the user set a target distance or was running a specific drill or game mode, include that context.

Device Calibration Metadata

Pass along calibration status, tilt/alignment info, or normalization mode (e.g., indoor vs. outdoor). This helps us contextualize data-quality flags.

Idempotency Keys on Webhooks

Include an X-Idempotency-Key header on webhook payloads so we can safely deduplicate retries without reprocessing.

Shot-Level Confidence Scores

If your sensor hardware produces confidence or data-quality indicators per metric (e.g., “ball speed was measured, spin was estimated”), surface those as a dataQuality object on each shot. Upstream quality metadata helps us make smarter analytics decisions.