The RunSignUp API has been extended to allow for better searching and sorting for races with a date range. We have added last_end_date and next_end_date to the response. We also added an option to search on start date only. If you add “search_start_date_only=T” to the URL, you’ll only get races based on the start date.
This is useful for our technology partners and affiliates who display races placed on RunSignUp on their calendars – like RunningIntheUSA.com and many others.
The RunSignUp Open API usually supports both JSON, XML and CSV formats. We have a preference for JSON, since that is the most common implementation of web service API’s today. Also, our largest partners – both The Race Director and RunScore – have implemented their interfaces in JSON.
We are expanding the Custom Results API to include a mechanism for providing notifications. The concept is that a list of participants can be uploaded to RunSignUp a week or two before a race and participants and their friends and families can then sign up for notifications. When race day comes, the timer will be able to post results via this API and their software to RunSignUp and we will take care of sending out all of the notifications. This fits with our expanding role of results capabilities and the ability for non-RunSignUp races to use our Results services.
This API can be used by technology partners who have scoring or timing systems that want to take advantage of RunSignUp Results capabilities and features like TXT and EMail notifications. The Custom Results API is an alternative to the Native API so there is more control over the look and feel of results, as well as the database structure.
The expanded API can be seen here – https://test.runsignup.com/API/race/:race_id/custom-results/POST. The new notification capability then allows the timer to upload a list of participants to RunSignUp and enable notifications. In particular:
The column_notification_placeholders array is optional. It maps a column to a placeholder in result notifications. If a segment has notification placeholders, a finish notification will be sent the first time a registration ID is seen. The registration IDs are specified through the row_registration_ids array. The registration ID for a row should not change after it is initially set.
RunSignUp will continue to keep our platform of web services open to make it easy for our technology partners to integrate and use our services to provide better solutions to the running marketplace.
We have been doing extensive additions to our Results Posting API in advance of some partners who will be private labeling our results platform. This is especially useful for timers or software developers who are creating their own scoring or timing software. By reusing RunSignUp Results, you can take advantage of our scalable platform with features like searchable results, notifications, finisher certificates, individual result pages with QR code capability, pace and age based calculations, divisions and age group reporting, etc. We license this platform on a very affordable basis to help timers get results to runners as quickly and easily as possible.
You can dig into the Results API here. As with all of our API’s, this is open source. That means you can build your own results engine if you want with this API as a wrapper to enable others like RunScore and The Race Director to communicate with you easily.
Here are a couple of the nice new features:
You can now upload alternate events when creating an event set. This is used for display purposes and if you are doing bib matching
If you send a registration that doesn’t belong to the event(s) for a result set, we still allow it if it is in the same race and year. So there’s not much need for you to use the event switching API anymore.
The Custom Results Page API has been updated so you can add, edit, and reorder rows in a custom report. This could work well for team results or cross country results and it allows for real-time results.
You can also get a glimpse of the new Results look and feel under development on our test server – for example https://test.runsignup.com/race/results/?raceId=1326. The API is on production now and the UI pieces will be introduced in mid November, 2014.
We 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
We have added the ability to set custom questions via the API. See it here – https://runsignup.com/API/race/:race_id/questions/POST.
We have a few technology partners and advanced customers who use our back end service and create their own custom user interface for a number of functions who needed this capability.
So this might not impact many people directly, but is great for expanding the overall Open RunSignUp Ecosystem to cover an ever expanding set of solutions for racing.
Here are samples using JSON and XML – Question API Samples
Here is a list of the functions (this might also be useful for other registration companies who are trying to figure out how what functionality needs to be included in custom question logic):
Warning: This is for developers.
We have extended our OpenAPI to allow for Race and User Creation and editing.
This API is being used by a couple of advanced users who have their own applications that have a need for creating races and users outside of the RunSignUp user interface. This is a powerful capability that allows a great deal of flexibility for other software applications who want to take advantage of RunSignUp’s powerful capabilities across areas like participant management, results, notifications, etc.
These API’s require additional security measures as we need to protect unauthorized use or attack. Please contact us to discuss why you need access to these API’s and we can give you the proper levels of authorization. You can get a testing account for via self serve here. Note that other API calls are available with a self serve authorization.
In other API news, we have added caching to OAuth. This increases performance for some of our technical partners who have high volume needs, as well as provides a fast experience for users with our technology partner systems.