Ingest laps | Outlap Docs

Send completed laps from any timing source. Provide user_id directly, or a transponder_id and Outlap resolves the driver from the event’s transponder roster. Laps that can’t be matched are still stored against the transponder, so you can assign them in Race Control afterwards.

There are two equivalent forms. Use the session form to attach laps to a specific session; lap numbers restart each session.

POST /v1/events/{eventId}/laps
POST /v1/events/{eventId}/sessions/{sessionId}/laps

Requires a key with the timing:write scope. See Authentication.

Path parameters

eventId string required

The event’s ID. It must belong to the club that owns the key.
sessionId string optional

Session form only. Attaches every lap in the request to that session.

Body

laps array required

Between 1 and 1,000 lap objects.

Lap object

lap_number integer required

Zero or greater.
lap_time_ms integer required

Lap time in milliseconds. Greater than 0 and no more than 24 hours.
s1_ms integer optional

Sector split. s2_ms, s3_ms and s4_ms work the same way.
speed_trap_kph number optional

Speed through the trap, in km/h.
is_valid boolean default: true

Set false for laps that shouldn’t count, for example cut or off-track laps.
invalid_reason string optional

Free text such as "cut T7". Shown to organisers.
transponder_id string optional

Used to resolve the driver when user_id is absent.
user_id string optional

The Outlap driver’s user ID. Overrides any transponder lookup.
recorded_at string optional

ISO 8601 timestamp. Defaults to the time of the request.

Response

Returns the number of laps stored.

inserted integer

Rows created.

Duplicates

This endpoint doesn’t de-duplicate: posting the same lap twice creates two rows. Retry only when you didn’t receive a response, and dedupe on your side, or mark the earlier lap invalid. For continuous feeds, use POST /stream, which ignores redelivered laps (per transponder, lap number and session).

curl -X POST https://fzfstcyowovukscxgdrh.supabase.co/functions/v1/timing-api/v1/events/EVENT_ID/laps \
  -H "Authorization: Bearer $OUTLAP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "laps": [
      {
        "lap_number": 1,
        "lap_time_ms": 92345,
        "s1_ms": 28110,
        "s2_ms": 31900,
        "s3_ms": 32335,
        "is_valid": true,
        "transponder_id": "TR-4421",
        "recorded_at": "2026-06-02T14:05:11Z"
      }
    ]
  }'

const res = await fetch(
  `https://fzfstcyowovukscxgdrh.supabase.co/functions/v1/timing-api/v1/events/${eventId}/laps`,
  {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.OUTLAP_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      laps: [
        {
          lap_number: 1,
          lap_time_ms: 92345,
          s1_ms: 28110,
          s2_ms: 31900,
          s3_ms: 32335,
          transponder_id: "TR-4421",
        },
      ],
    }),
  },
);
if (!res.ok) throw new Error((await res.json()).error);
console.log(await res.json());

import os, requests

res = requests.post(
    f"https://fzfstcyowovukscxgdrh.supabase.co/functions/v1/timing-api/v1/events/{event_id}/laps",
    headers={"Authorization": f"Bearer {os.environ['OUTLAP_API_KEY']}"},
    json={
        "laps": [
            {
                "lap_number": 1,
                "lap_time_ms": 92345,
                "s1_ms": 28110,
                "s2_ms": 31900,
                "s3_ms": 32335,
                "transponder_id": "TR-4421",
            }
        ]
    },
)
res.raise_for_status()
print(res.json())

{ "inserted": 1 }

{ "error": "invalid lap_time_ms" }

curl -X POST https://fzfstcyowovukscxgdrh.supabase.co/functions/v1/timing-api/v1/events/EVENT_ID/sessions/SESSION_ID/laps \
  -H "Authorization: Bearer $OUTLAP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "laps": [ { "lap_number": 5, "lap_time_ms": 88420, "user_id": "USER_UUID" } ] }'