Core Endpoints — Launch Monitor & Session Partners
These integrations cover hardware launch monitors (e.g., Trackman, FlightScope, Foresight GCQuad, Garmin R10, Rapsodo MLM2PRO) and simulator platforms (e.g., GSPro, Full Swing) that produce ball-flight and club-delivery telemetry during practice sessions.
Your API must expose the following endpoints (or functional equivalents) for us to build a working integration.
Every integration also needs the authentication and account-linking
endpoints from the platform conventions, and
should send webhooks for session.completed, session.edited and
session.deleted.
Session Listing & Retrieval
Section titled “Session Listing & Retrieval”GET
/sessionsList practice sessions for the authenticated user.
- Should support date-range filtering (
?startDate=&endDate=). Required for production-scale background sync. - Should support pagination. Required for users with large session histories.
- Response should include session-level metadata: session ID, start time, end time, device model, and shot count.
GET
/sessions/{sessionId}Return full detail for a single session, including all shots.
GET
/sessions/{sessionId}/shotsReturn the ordered list of shots within a session.
- Each shot must include a unique, stable
sourceId(see Data Schema). - Shots must be ordered by timestamp or sequence index. Our processing pipeline depends on correct shot ordering.