In this Academy Live session, Jesse Green, Adam Rolf, and Matt Tometz covered two sides of the same coin:
-How to access your 1080 data more easily through the API for athlete monitoring
-How to actually use that data for sprint testing, velocity profiling, and programming decisions
From API keys and GitHub walkthroughs to resisted sprint testing, load-velocity profiling, and integrating motorized resistance into skill development, this webinar gave both technical and tactical insight. Whether you're a data-savvy coach or just starting to explore beyond the default reports, there's something here for you.
1080 Motion API for Sprint Data and Athlete Profiling
What if your training data could flow seamlessly from the 1080 Motion cloud into your own dashboards, programming tools, or athlete management systems?
That’s exactly what our API is designed to do.
In a short but info-packed walkthrough, Jesse shows how easy it is to generate your own API key, access our GitHub, and start visualizing sprint performance metrics and athlete testing data using R or Python. Whether you want full access to raw sprint velocity, power outputs, force metrics, and positional data—or simply want to combine your 1080 data with other platforms like Teamworks, Kinduct, or RockDaisy—the API gives you full control.
(also included is the rest of the webinar with the live answers to the Q&A)
It’s not just about coding. It’s about connecting your 1080 data with the rest of your ecosystem—force plates, HRV, AMS, surveys, etc. The more context you have, the better decisions you can make.
"Ask Me Anything" for Resisted Sprint Training and Motorized Resistance
But most of this webinar wasn’t about code. It was a deeper conversation about how to actually use the data, from week-to-week testing strategies to how motorized resistance can support skill development in sport. Here are some of the standout Q&A moments:
What’s the best way to structure testing across a multi-week program?
Think fewer targets, more arrows. If you're changing the test every week (different loads, distances, setups, etc.), you can’t assess change over time. Instead, pick 1–2 foundational sprint tests and track them weekly. For example, always include a 15-yard sprint with light load (2-3kg), even as your program progresses. That gives you a stable trendline across phases.
How do you balance phase-specific training with ongoing monitoring?
Let’s say you’re in Phase 1 with heavy 50% velocity decrement sprints (e.g. 20kg). Do your resisted sprint reps at 20kg and track progress within that 4-week phase. But also make sure to get your lighter reps in, preferable near the beginning of the session, to monitor from Week 1 to Week 12. So you’re capturing both: what’s improving within the phase and across the entire program.
What should I actually look at in the data?
Don’t start with the tech—start with what you want to monitor, change, and train. If you want to improve 20-yard time, ask: Does this athlete need more horizontal force production, a higher max velocity, or a different velocity decrement for sprint training? Profile that, build a plan, and retest with purpose. It’s easy to get lost in metrics if you don’t have a framework.
What does “training is testing” actually look like in practice?
It’s not just about scheduling a test once a week, it’s about using training itself as the test. Whether it's your phase-specific drill like a 20kg sprint, or a weekly check-in at 2kg, you can track how that changes over time. The best part is, those things you'd be doing anyways.
Then "training is testing" turns into "testing informs training." Instead of checking in once every 6 or 12 weeks, the athlete’s data can guide decisions on a daily and weekly basis. Decisions can be to keep pushing, cut back, or simply stay the course. The more consistently you collect and interpret that data, the more confidently you can adjust the program in real time, not after the fact.
How can skill coaches or sport-specific coaches use 1080 more effectively?
We're seeing more skill coaches use both resistance and data to support their training, instead of letting speed training exist in isolation. Wide receiver coaches are doing route drills with light resistance or hockey players train with sticks in hand on the 1080 Sprint, and golfers are loading up torso rotation while holding their club on the 1080 Cable or Quantum Syncro.
Think of it as constraint-based skill learning. The resistance or assistance can help an athlete feel better positions—shin angle, trunk lean, or sequencing—not just build force. Combine this with an expert coaching eye and a thoughtful program, and you have a powerful combination.
In Summary
The best technology doesn’t just give you data, it gives you direction. Whether it’s syncing your 1080 data with your own dashboard or using weekly sprint testing data to decide whether to push or pull back, the end goal is the same: training decisions that make athletes better. The API opens the door to more customized workflows, and the training conversation helps you act on what the numbers say. Start simple, test with purpose, and use your data to drive progress.
Published: September 15, 2025