API Sharing for ultra signup race links on websites

A simple, permission-based API with basic race info, finisher data, runner-owned results, and direct links back to UltraSignup would make it much easier for community platforms, clubs, and coaches to surface and share events accurately.
UltraSignup already interacts with data from a variety of sources, so offering a lightweight API outward seems like a natural next step. It would reduce the need for scraping, help runners pull their own results into training or coaching tools, and ensure that any race information shown elsewhere always routes back to UltraSignup as the source.
Thanks for considering it and for everything you continue to do for the sport.

We’ve been working on some API improvements and this seems to fit the spirit of that really well. I would value hearing more about some specific use cases you have in mind. When it comes to sharing data with third-party training apps, for example, this could be done as an integration witih specific apps (easier to connect for users) or as an open API (for developers). Both approaches require the API, but use cases would determine which would likely be better for end-users. Thoughts (and differing opinions) welcome!

Thanks Jase, I’m working on a site that provides write ups for trail and ultra races and contains available race reports to allow runners to dive deeper into the race etc. I’d like the list to be comprehensive and to be able to include links to the races on ultrasignup to make it easier for participants to sign up.

Modern API integration is becoming essential for sports and race management platforms. Sharing race links dynamically across websites can improve visibility, reduce manual work, and create a more connected experience for runners. Hopefully this feature gets implemented soon. Similar web integration strategies are becoming more common in projects handled by <a href="https://dotitmedia.co.uk/" target="_blank">Dot It Media UK</a>.

Any update on this?

I’m building Medaling with Friends (https://medalingwithfriends.com), a consent-first, private-by-default app where runners see their friends’ and clubs’ race schedules and results in one place. A permission-based UltraSignup API like this is the missing piece.

Ideally this is a per-runner OAuth authorization — the same model RunSignup already offers. A runner connects their UltraSignup account once, and the app pulls their own verified race history and results (keyed to their account, so no same-name mix-ups) with their explicit permission.

Concretely, what a connected app would use — all scoped to what the runner already permits:

• Basic race + event info (name, date, distance, location, official link) so a runner can add a race to their schedule and we can link straight back to the UltraSignup page — we drive registrations to you, never around you.
• Runner-owned results — a signed-in runner pulling their own verified finish history (keyed on their UltraSignup participant id, not name — this also sidesteps the same-name mix-ups people are reporting elsewhere on this board).
• Finisher data for a race, scoped to what’s already public on the results page, so we can show “who’s racing / who finished” among people a user is actually connected to.

A documented, permissioned API would let community platforms, clubs, and coaches surface UltraSignup events accurately and send traffic and registrations back to you — a clear win for RDs and runners both. Happy to be an early integration tester.