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.