> For the complete documentation index, see [llms.txt](https://help.runonrufus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.runonrufus.com/public-api/introduction-to-rufus-cloud-api.md).

# Introduction to RUFUS Cloud API

The API has evolved from a simple ingestion layer into a production-ready platform. It maintains full backward compatibility with existing v0 integrations—ensuring current devices and workflows continue to operate unchanged—while introducing stronger validation, improved security, and better protection against duplicate data, stale telemetry, and abusive traffic.

At its core, the API still revolves around three fundamental resources: **devices**, **sessions**, and **passings**. Devices connect to the cloud and create timing sessions, which act as containers for race passings. These passings can be consumed in real time or accessed later, enabling flexible workflows across timing operations.

On top of this foundation, the API now expands into two key areas:

* **Device Telemetry & Health**\
  Devices can report operational status (battery, temperature, GPS, connectivity, and more), enabling real-time monitoring and better field control.
* **Event & Participant Integration**\
  A new public layer allows authenticated clients to access event data and manage participants, enabling deeper integrations with registration systems, apps, and external platforms.

With improved reliability, stricter data integrity, and expanded capabilities, the RUFUS Cloud API is designed to support scalable, real-world race operations—while remaining simple and flexible to integrate.


---

# 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://help.runonrufus.com/public-api/introduction-to-rufus-cloud-api.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.