Bring your idea to life with data
A useful first version can start with examples. The next step is to show a rider, a route or a result you recognise—using data you are authorised to process.
Start with one rider or one course. You do not need to upload months of files before finding out whether the view is useful.
Choose the job, then the data#
| What you are building | Data to start with | MovePacket capability |
|---|---|---|
| A rider dashboard or session review | Authorised FIT or FIT.GZ activity files | Data Connect |
| A course brief or climb view | A GPX course | Event Intelligence |
| A simple calculator | Entered values or labelled sample inputs | May not need a data API |
| A custom workflow with saved notes or settings | Project-owned records | The hosted project's private-record API, through an authorised server or builder |
A GPX course describes a route. It is not a substitute for a FIT recording with power, heart rate and other measurements. Files can contain precise locations and personal information; use only the data needed for the task.
Check access before importing#
In Integrations → Capabilities, explore the capabilities. Ask your connected builder to inspect the project's capabilities and data connection before it builds against them.
Customer trial accounts do not currently have activity imports or athlete-platform connections enabled. Data Connect and Event Intelligence require separate authorised beta access. Core setup and a project builder connection do not grant it automatically. A listing marked available to authorised workspaces is not the same as activated for your account.
If the access you need is missing, keep examples labelled and contact MovePacket about the intended use. Do not paste athlete records into chat or place them in a public page to bypass the access boundary.
Import in an enabled workspace#
For an authorised workspace with activity imports, use Data → Import rides, choose the athlete and record the permission context. Select FIT or FIT.GZ files and review the per-file results. Athlete data connections explains batch limits, duplicates and resuming an import.
For a course tool, the Event Intelligence guide explains GPX input and the private analysis result. Automatic TrainingPeaks or device-account sync is not connected today.
Tell your builder where data belongs#
Use MovePacket Data Connect for athlete and training data. Check which athletes and API access are available for this project. Start with one authorised rider and a useful date range. Preserve missing values and label the source and date of the data. Explain any missing server-side connection before trying to show live records.
Uploads and future supported provider adapters feed the MovePacket data layer. Your dashboard should not be asked to connect to SEMIPRO.coach as a default data source. SEMIPRO is a reference application.
Project publishing currently serves browser files, not arbitrary backend code. A private-record API or athlete-data key must stay on an authorised server or with the builder; it cannot be embedded in the page. A file opened temporarily in a browser preview is not necessarily imported or saved in MovePacket.
Know when it is real#
Check that the rider, dates, units and route match your source. Try another record, an empty period and a missing measurement. Reload to confirm which information persists. A realistic chart alone does not prove a live connection.
Keep the project private while working with personal data. Access & sharing explains the current audience options.
Intervals.icu for coaches#
Planned · not connected yet. Intervals.icu is the first planned athlete-platform source for Data Connect. Find its provider card in Integrations → Athlete platforms to request the connection. No credentials are collected and no sync starts from that request.
The intended flow is: authorise the rider data, bring supported records into Data Connect, then use the same MovePacket data connection in your dashboards and preferred builder. Athletes will not need to buy MovePacket just to authorise their data.
Intervals.icu's documented OAuth connection grants access to the athlete who authorises it. Signing in as a coach does not automatically authorise every coached or followed athlete. Its API guide directs multi-user applications to OAuth. A broader coach-key setup needs a confirmed supported approach and secure credential handling before we can offer it.
Initially, connection permissions will determine which records can be used. Later, coach-controlled filters can narrow that authorised set by rider, date or activity type. Filters cannot add permission, and the absence of a filter will not mean unrestricted access or an automatic import of everyone you follow. The connection is not a replacement for any required permission to process athlete data.
Automatic imports remain unavailable until the supported access flow, provider approval and credential-security checks are complete. Some upstream data is restricted from onward sharing; Garmin-sourced activity data also carries attribution requirements. We will preserve source information and show unsupported records as unavailable rather than promise a complete mirror.
Provider references: API access guide, athlete OAuth access boundary, API terms and attribution.
Data Connect for agent-built software#
Use Data Connect to discover authorised athletes and domain permissions with the app’s server connection. Owners configure access in Data → athlete → App access. Source files, observations, memory and dated context remain distinct. Clinical data and unrestricted provider sync are not enabled.