# Using the Race App with Third-Party Software

The RUFUS Race App can also integrate with third-party timing or race management software via the **RUFUS Public API**.

In this scenario, RUFUS Cloud remains the access and device control layer.

## Architecture Overview

Race App → RUFUS Cloud → RUFUS Public API → Third-Party Software

The Race App sends:

* Passings
* Race Actions *(data not available via API)*
* Alerts *(data not available via API)*
* Chat messages *(data not available via API)*

These are exposed via the Public API for external systems to consume.

## What Third-Party Systems Can Receive

Depending on integration design:

* Manual passings
* Status changes *(data not available via API)*
* Race Alerts *(data not available via API)*
* Session metadata

The third-party system handles:

* Result calculations
* Classification logic
* Display or publication

## Device and Token Management

Even when using third-party software:

* Race Apps are still created in RUFUS Cloud.
* Access tokens control judge access.
* Token rotation invalidates sessions.
* Audit remains available at Cloud level.

## Integration Considerations

When integrating with external software:

* Ensure real-time webhook or polling strategy.
* Maintain consistent checkpoint mapping.
* Align timestamp handling (device time vs server time).

## Operational Best Practices

* Test full data flow before race day.
* Validate duplicate protection logic.
* Monitor API logs during live operations.

## Summary

The RUFUS Race App can operate independently with Race Manager or act as a structured field input layer for third-party systems via the RUFUS Public API.

In all cases, RUFUS Cloud manages access, sessions, and traceability.


---

# Agent Instructions: 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:

```
GET https://help.runonrufus.com/rufus-cloud/race-app/using-the-race-app-with-third-party-software.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.