> ## Documentation Index
> Fetch the complete documentation index at: https://partner-help.letsdothis.com/llms.txt
> Use this file to discover all available pages before exploring further.

# mika:timing

> Sync participant registrations to mika:timing and receive bib numbers back automatically.

<Info>
  The mika:timing integration is available to select accounts. Contact your
  account manager to enable it.
</Info>

The mika:timing integration keeps your participant list in mika:timing up to
date automatically. When a participant registers or updates their registration,
their details are pushed to mika:timing without any manual export. Bib numbers
assigned in mika:timing are sent back and applied to the participant's record
automatically.

## Before you start

You need a mika:timing account and a meeting created in mika:timing for your
event. Have your account and meeting details ready — your account manager will
ask for them during setup.

## Setting up the integration

Setup is per event and is handled by the Let's Do This team. Contact your
account manager with:

* Your mika:timing account details
* The mika:timing meeting for your event
* Which mika:timing race each of your ticket types maps to

Once configured, new registrations and updates sync automatically, and existing
registrations are backfilled so participants who registered before the
integration was enabled also appear in mika:timing.

## What data is sent to mika:timing

Every synced participant sends the following standard fields:

* First name and last name
* Email address
* Sex
* Date of birth
* Address (street, city, state, postcode, and country)
* Phone number

Additional fields from your registration questions, such as nationality, can be
mapped during setup.

## Receiving bib numbers

When mika:timing assigns a bib number to a participant, it is sent back to
Let's Do This and appears on the participant's record without any manual
import. Updates are applied in the order they changed at the timing provider,
so an older value never overwrites a newer one.

<Note>
  For timing providers: the inbound message contract is documented in the Timing
  section of the [API reference](/api-reference/overview).
</Note>