Custom Results API and UI Improvements

Custom ResultsWe have expanded the Custom Results API and the user interface for displaying custom results. The Custom Results API allows an application to upload results and do custom formatting and upload more generic data. Here is an example used to upload Age Group Results and other Awards from RunScore.

There are two key upgrades:

  • Setting Data Types – this allows us understand the data being uploaded better to do better sorting and searching
  • Display improvements – Paging, Sorting and Searching of results

Author: RunSignUp

RunSignUp is the leading innovator of online tools for race registration, race day solutions, and running clubs. Services include RunSignUp for registration, RunSignUp Go for Race Day, RunSignUp RD Go for Timers, RunSignUp Clubs to enable membership management, and RaceJoy for mobile experiences. More than 10,000 race directors, timers, running club officers and running stores use these services today, including leading organizations like the Boilermaker Road Race, Crim Festival of Races, Pittsburgh Three Rivers Marathon, Inc., Fifth Third River Bank Run, Blacklight Run, Bubble Run, Night Nation, Mercedes Marathon, Kentucky Derby Festival, Leone Timing, KC Running Company, Compuscore Timing, Knoxville Track Club, Pikes Peak Road Runners, Gulf Coast Runners, Columbus Running Company, Playmakers Running Store and many more. In 2015, over 10,000 races used the system to register more than 2.7 million participants. In 2016 over 14,000 races will use the system to process over 4.3 million paid registrations. Services are free except for processing fees when conducting monetary transactions such as race registration or club membership renewal. RunSignUp is founded by runners for runners, using technical capabilities to bring the power of cloud computing to benefit the running community. For more information, visit

2 thoughts on “Custom Results API and UI Improvements”

    1. They can trigger results if there is a mapping done to the registration id of the runner and the data is mapped – for example gun or chip time and place. The way the notifications work is off of specific fields of data in RunSignUp. Custom Results are typically used to upload undefined and un-mapped data. For example, today the RunScore integration does the notification triggers by uploading “native” data via the integration of registration id and mapping of fields. The custom upload is done for things like Age Group Reporting. Take a look at for an example of each.

      We are doing some development now with RunScore that will change some of this, so if you are a RunScore user, watch that newsgroup. If you are a developer looking to integrate with the API, let us know and we can have deeper conversations about approaches.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s