Core Endpoints — Rounds & Mobile App Partners
These integrations cover GPS-based round trackers, mobile scoring apps, and wearable devices that capture on-course shot locations, scores, and club usage during played rounds.
Every integration also needs the authentication and account-linking
endpoints from the platform conventions, and
should send webhooks for round.completed, round.edited and round.deleted.
Round Listing & Retrieval
Section titled “Round Listing & Retrieval”GET
/roundsList completed rounds 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 round histories.
- Response should include: round ID, course name, course ID, round date, total score, and number of holes played.
GET
/rounds/{roundId}Full round detail including hole-by-hole breakdown and all shots.
GET
/rounds/{roundId}/holesHole-level data for the round.
- Each hole must include: hole number, par, and score at minimum. Putts are strongly recommended.
GET
/rounds/{roundId}/shotsAll shots in the round, ordered by hole then shot-in-hole sequence.
- Each shot must include a unique, stable
sourceId(see Data Schema). - Shots must be ordered by hole number then by shot sequence within the hole. Our processing pipeline depends on correct shot ordering.
User Club Bag (if available)
Section titled “User Club Bag (if available)”GET
/users/me/clubsReturn the user’s configured club bag.
- Each club: club type, brand, model, loft (if known).
- This lets us cross-reference club selections in shot data.