Appearance
Sessions & race data
Paths below are relative to /api/integrations/v1. The reference lists all filters and response fields.
Sessions and tracks
List your sessions with GET /sessions, then fetch GET /sessions/{id} for track IDs.
| Response field | Send on the next request |
|---|---|
next_before_id | before_id |
next_before_track_id | before_track_id |
next_cursor | cursor |
Continue until the next-page value is null.
GPS
GPS endpoints return committed boat recordings within the session window:
time_epoch,lat,lng; timestamps are UTC Unix seconds with the track offset already applied.- Null coordinates mark invalid fixes. Preserve gaps rather than joining across them.
- Use up to 5,000 points per page and cache completed downloads.
Cursors expire after 15 minutes. If a cursor expires or the source changes, restart that track; keep other completed downloads. Live or unsupported sources return an unavailable reason.
Events and analysis
Discover an event, resolve access to a day, then follow its session data links. These reads use your existing account access and spend no report allowance or FLO credits.
Read the analysis catalog for race IDs, snapshots and readiness. Results, start statistics and comparisons use saved analysis; they do not automatically recalculate it. Wind is the configured session series.
For paginated results, starts or wind, retain the returned snapshot and send it as expected_snapshot where required. Missing data is not zero. Race positions apply to that race, not the full regatta.