# Build around your athletes’ data.

The hardest part of custom coaching software is getting reliable access to the athletes you coach. MovePacket is building the connections and dependable records underneath that software.

Start today with an authorised original FIT file. The private beta preserves it, tracks processing and returns decoded data through an authenticated API. Automatic athlete connections are the next priority.

<div class="docs-flow" aria-label="Upload a FIT file, process the activity, build your app"><span>01 <b>Original FIT</b></span><i>→</i><span>02 <b>MovePacket</b></span><i>→</i><span>03 <b>Your app</b></span></div>

<div class="docs-cards"><a href="/docs/quickstart"><small>START HERE · NODE.JS</small><h3>Your first activity ↗</h3><p>Upload, wait for processing, and verify the original with one runnable example.</p></a><a href="/docs/api-reference"><small>THE CONTRACT · REST API</small><h3>Explore the API ↗</h3><p>Endpoints, request formats, responses, authentication, and limits.</p></a></div>

## Infrastructure for your expertise

MovePacket serves independent endurance coaches and small coaching businesses first. The underlying product stays sport-agnostic: ingest, store, structure, permission, transform and deliver. Your application supplies the coaching or performance judgment.

Connectivity comes before the breadth of tools built on top. Athlete identity and authorisation, supported historical imports, new-activity delivery and visible connection health are the next priorities. [See the current routes and roadmap](/docs/connections).

## A small API with a clear job

MovePacket accepts a FIT activity, validates the file, and queues it for decoding. Your app receives an activity ID immediately and can check back until the data is ready. Every activity has a preserved original, a SHA-256 checksum, and a processing status.

The beta exposes decoded Garmin FIT messages. It does not yet normalize data across providers or add coaching interpretation. See the [data model](/docs/data-model) for the exact response shape.

## Choose your starting point

| You want to… | Start here |
| --- | --- |
| Try a file without writing code | [Private workspace](/upload) |
| Understand how to get athlete data | [Athlete connections](/docs/connections) |
| Inspect provenance and verify an original | [Records & responsibility](/docs/records) |
| Connect your application | [Quickstart](/docs/quickstart) |
| Keep keys and activity data private | [Authentication](/docs/authentication) |
| Handle processing, retries, and duplicates | [Processing and reliability](/docs/processing) |
| Give an AI coding assistant the contract | [Build with AI](/docs/ai-tools) |

## What the beta supports

| Capability | Status |
| --- | --- |
| FIT upload, validation, and decoding | Implemented; requires an enabled beta environment |
| Original file and decoded JSON retrieval | Implemented; authenticated access |
| Activity search, status filters, and pagination | Implemented |
| Browser workspace | Implemented; invited access |
| Original integrity verification and record metadata export | Implemented in the workspace Record tab |
| Athlete invitations and athlete-level app grants | Planned |
| Automatic device connections and historical sync | Planned |
| Outbound webhooks and delivery history | Planned; use status polling today |
| MovePacket MCP server and packaged SDKs | Planned |
| Public signup and self-service API keys | Planned |

These guides describe the current beta contract. Follow the availability notice above before sending files to a hosted environment.