- API Overview
- Getting Started
- API Keys
- API Methods
- Error Codes
- Code Examples
- API Playground
RunSignUp has implemented a robust and completely open API with a set of partners to make sure our web service is as open as possible. The benefit to the running community is that RunSignUp can be used with many other services for timing, results, and any website. We also hope the API and the various components we have open sourced serve as spurs for more innovation and eases integration points for everyone in the community.
Today our API covers the following areas:
- Results - Post Results to RunSignUp in bulk or individually in real time. Get results from RunSignUp.
- Participants - Download participant information. We also will be adding Upload of participant information.
- Affiliates - Allows other websites to become part of our Affiliate Program and list races on their own websites.
Our API will continue to expand as we see opportunities for working with other technology in the running community. We also look forward to adopting other Open API efforts that others develop.
We want to thank our earliest API users for inspiring us to build this well - RunningintheUSA.com (the most popular site for finding races in the US), The Race Director (One of the leading timer systems), and RunScore (the other leading timing system). We also want to thank Eric Cone of RaceIt for sharing their early API with us for Participant integration with The Race Director and RunScore.
Our API has been released under a "free-use" Apache license. This permits the unrestricted use and distribution of the API, the interface's header files, documentation and programming examples, but does not apply to the RunSignUp content or services. RunSignUp content and services remain under the normal service agreements.
As one example, this means another service may use our API to provide access to the RunSignUp system via the API. The Race Director and RunScore capability to download participants from RunSignUp is a good example as they provide the basic access, but the user of their system is accessing the real service and data via their RunSignup login.
Another example is that one of our competitors like Active.com could freely take our API and use that to make it simple to download results directly from a timing system like Chronotrack. Neither Active.com or Chronotrack would need to have any involvement with RunSignUp and only need to meet the terms of the Apache license.
Please provide feedback to us on any ideas for expansion and collaboration by sending an email to .