> For the complete documentation index, see [llms.txt](https://docs.racemap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.racemap.com/integrations.md).

# Integrations

Timing systems, devices and platforms that exchange data with RACEMAP, and the generic interfaces for everything that is not listed yet.

RACEMAP exchanges data with timing software, timing hardware, device clouds and result platforms. Every integration runs in one of two directions:

* **Into RACEMAP** — a system sends detections, locations or participants to RACEMAP.
* **Out of RACEMAP** — a platform reads locations, times and ranks from the RACEMAP APIs.

Systems that are not listed can still connect through the generic interfaces further down.

### Systems RACEMAP works with

| System                                         | What the integration does                                 | Guide                                                                                     |
| ---------------------------------------------- | --------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| [RACE RESULT](https://www.raceresult.com/)     | Use ubidium, Track Boxes and decoders as GPS trackers     | [Add RACE RESULT readers](/tracker-management/add-race-result-readers.md)                 |
| [RACE RESULT](https://www.raceresult.com/)     | Drive predictive tracking with timing detections          | [RACE RESULT](/prediction/timekeeping/raceresult.md)                                      |
| [RACE RESULT](https://www.raceresult.com/)     | Forward Track Pings straight to the RACEMAP server        | [Track Box forwarding](/gps-devices/track-box-forwarding.md)                              |
| [RACE RESULT](https://www.raceresult.com/)     | Synchronize participants into a RACEMAP event             | [RACE RESULT import](/api-import-and-export-data/import-basics/metadata-import-via-rr.md) |
| [MyLaps](https://www.mylaps.com/)              | Send reads from the local timing software to RACEMAP      | [RACEMAP forwarder](/prediction/timekeeping/other-timingsystem/forwarder.md)              |
| [ChronoTrack](https://www.chronotrack.com/)    | Send reads from the Simple Client to RACEMAP              | [RACEMAP forwarder](/prediction/timekeeping/other-timingsystem/forwarder.md)              |
| [Wiclax](https://www.wiclax.com/)              | Import RACEMAP passings and show live locations in Wiclax | [Wiclax](/integrations/wiclax.md)                                                         |
| [Insiders](https://insiders.live/)             | Receive 10 Hz device data from the insiders cloud         | [Insiders GPS trackers](/gps-devices/insiders.md)                                         |
| Garmin, Polar, Suunto and other sports watches | Submit recorded activities as GPX, KML or TCX             | [Activity upload](/live-tracking/activity-upload.md)                                      |
| WMS map servers                                | Show an external map layer on the tracking map            | [External map layer](/tab-map/external-map-layer.md)                                      |

### Connect a system that is not listed

Two generic interfaces cover most platforms. Neither needs work on our side.

Any backend that can send HTTP requests writes locations into a virtual tracker:

{% content-ref url="/pages/9Ben7jHdAEIeamrBMGe4" %}
[HTTP tracker](/gps-devices/http-tracker.md)
{% endcontent-ref %}

Any application reads locations, distances, times, ranks and participants from the data APIs:

{% content-ref url="/pages/-LhnxBUqIeaJoZDskAT\_" %}
[Data APIs for live geodata](/api.md)
{% endcontent-ref %}

Have you integrated RACEMAP data and want your platform listed here? Write to <info@racemap.com>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.racemap.com/integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.