MYLAPS API Integration | Speedhive Event Results & Live Timing Data

What is MYLAPS integration?

MYLAPS provides transponder-based timing systems and software (such as Orbits) for motorsport, karting, cycling, running and other events, plus the Speedhive platform for published results and live timing. Speedhive's Event Results API has a publicly accessible OpenAPI (Swagger) specification covering organizations, events, sessions, results and laps. Live timing data access is different: MYLAPS controls it through an SDK provided after screening and an NDA, and the event's timer owns the data.

Who uses MYLAPS?

MYLAPS systems are used by race tracks, karting circuits, cycling and running events, and timing companies worldwide. Integration projects include results websites, driver performance apps, and broadcast or in-venue displays.

Key components

• Speedhive Event Results API: OpenAPI-documented results data: organizations, events, sessions, results, laps

• Orbits: MYLAPS timing and scoring software for motorsport; can publish a Speedhive live feed

• Transponders & decoders: Hardware that detects passings at timing loops

• MYLAPS SDK: Live data access granted by MYLAPS after approval

How integration works

• Event Results API (REST/JSON): for published results, laps and sessions

• Speedhive live feed: enabled from Orbits' Distribution tab to publish live timing to the Speedhive app

• SDK (by approval): for direct live passing data; needs the timer's consent and MYLAPS approval

What SportsFirst builds

• Results ingestion: Read the timer's output (files, serial or API) into your platform in real time

• Live results web & apps: Publish times, splits and rankings to web, apps and social

• Scoreboard & graphics output: Push confirmed times to video boards and broadcast graphics

• Entries & start lists: Sync registrations and start lists into the timing workflow

• Offline resilience: Buffering and local operation for venues with poor connectivity

Example use cases

• Race tracks & karting: driver history, lap analysis and leaderboards

• Endurance events: results pages and athlete notifications

• Broadcast/in-venue: leaderboards from confirmed timing data

Why work with SportsFirst?

• Timing-grade data handling: we keep precision, penalties and status flags intact end to end

• Offline-first design: results keep flowing on the local network if the internet drops

• One source of truth: a single confirmed time feeds boards, graphics, web and apps

• Discovery first: we map your timing workflow and hardware before writing code

SportsFirst is an independent development studio. We are not affiliated with or endorsed by MYLAPS. MYLAPS and Speedhive are trademarks of their respective owners.

FAQ

Q1. Does MYLAPS have a public API?

Partly. Speedhive's Event Results API has a public OpenAPI specification. Live timing access is through an SDK MYLAPS grants after approval.

Q2. Who owns MYLAPS live timing data?

According to MYLAPS support, the timer running the event owns the data; you need their agreement as well as MYLAPS approval.

Q3. Can I build a lap analysis app with MYLAPS data?

Yes, using published results and laps from the Event Results API, subject to MYLAPS terms.

Q4. Can SportsFirst help with MYLAPS integration?

Yes. We build results apps, leaderboards and data pipelines on top of MYLAPS and Speedhive data.