In order to use RunSignup, your browser must accept cookies. Otherwise, you will not be able to register for races or use other functionality of the website. However, your browser doesn't appear to allow cookies by default.
If you still see this message after clicking the link, then your browser settings are likely set to not allow cookies. Please try enabling cookies. You can find instructions at https://www.whatismybrowser.com/guides/how-to-enable-cookies/auto.
API calls require api_key and api_secret parameters in the URL. Be sure to include "https" in front of all API calls to keep your API credentials secure.
IMPORTANT! All times in the API are in Eastern Time unless otherwise noted.
All fields will have an associated datatype. Below are the field types used in the API.
|Data Type||Description||Valid Values|
||A password string.|
||Floating point number.|
||Boolean value.||T, F|
||Comma separated list of integer IDs.|
||Comma separated list of integer strings.|
||Response or request format. You can submit GRU files from RunScore and The Race Director by specifying CSV. Not all methods support each format.||xml, json, csv|
||Date formatted as "YYYY-mm-dd", a timestamp, or one of the strings "today" and "tomorrow".|
||24-hr time formatted as "hh:mm:ss".|
||Date and time formatted as "YYYY-mm-dd hh:mm:ss" where time is in 24-hour format.|
||Gender as either "M" or "F".||M, F|
||Phone number formatted as "xxx-xxx-xxxx".|
||Two letter state or province abbreviation.|
||Two letter ISO 3166-1 alpha-2 country code.||US, AD, AE, AF, AG, AI, AL, AM, AO, AQ, AR, AS, AT, AU, AW, AX, AZ, BA, BB, BD, BE, BF, BG, BH, BI, BJ, BL, BM, BN, BO, BQ, BR, BS, BT, BV, BW, BY, BZ, CA, CC, CD, CF, CG, CH, CI, CK, CL, CM, CN, CO, CR, CU, CV, CW, CX, CY, CZ, DE, DJ, DK, DM, DO, DZ, EC, EE, EG, EH, ER, ES, ET, FI, FJ, FK, FM, FO, FR, GA, GB, GD, GE, GF, GG, GH, GI, GL, GM, GN, GP, GQ, GR, GS, GT, GU, GW, GY, HK, HM, HN, HR, HT, HU, ID, IE, IL, IM, IN, IO, IQ, IR, IS, IT, JE, JM, JO, JP, KE, KG, KH, KI, KM, KN, KP, KR, KW, KY, KZ, LA, LB, LC, LI, LK, LR, LS, LT, LU, LV, LY, MA, MC, MD, ME, MF, MG, MH, MK, ML, MM, MN, MO, MP, MQ, MR, MS, MT, MU, MV, MW, MX, MY, MZ, NA, NC, NE, NF, NG, NI, NL, NO, NP, NR, NU, NZ, OM, PA, PE, PF, PG, PH, PK, PL, PM, PN, PR, PS, PT, PW, PY, QA, RE, RO, RS, RU, RW, SA, SB, SC, SD, SE, SG, SH, SI, SJ, SK, SL, SM, SN, SO, SR, SS, ST, SV, SX, SY, SZ, TC, TD, TF, TG, TH, TJ, TK, TL, TM, TN, TO, TR, TT, TV, TW, TZ, UA, UG, UM, UY, UZ, VA, VC, VE, VG, VI, VN, VU, WF, WS, XK, YE, YT, ZA, ZM, ZW|
||Units for distance: K: km, M: miles, y: yards, and m: meters.||K, M, y, m|
running_race - Run or Run/Walk
virtual_race - Virtual Race / Challenge
nonprofit_event - Nonprofit Event
running_only - Run Only
walking_only - Walk Only
race_walk - Race Walk
wheelchair - Wheelchair Race
triathlon - Triathlon
duathlon - Duathlon
bike_race - Bike Race
bike_ride - Bike Ride
mountain_bike_race - Mountain Bike Race
gravel_grinder - Gravel Grinder
fundraising_ride - Fundraising Ride
trail_race - Trail Race
open_course_trail - Open Course Trail
ultra - Ultra
hike - Hike
obstacle_course - Obstacle Course
adventure_race - Adventure Race
swim - Swim
swim_run - SwimRun
aqua_bike - Aquabike
ski - Ski
paddle_sports - Paddle Sports
disc_golf - Disc Golf
clinic - Clinic
expo - Expo
other - Other
|running_race, virtual_race, nonprofit_event, running_only, walking_only, race_walk, wheelchair, triathlon, duathlon, bike_race, bike_ride, mountain_bike_race, gravel_grinder, fundraising_ride, trail_race, open_course_trail, ultra, hike, obstacle_course, adventure_race, swim, swim_run, aqua_bike, ski, paddle_sports, disc_golf, clinic, expo, other|
If there is an issue with your request, you may get responses such as below.List of Error Codes
<error> <error_code>6</error_code> <error_msg>Key authentication failed</error_msg> </error>
<error> <error_code>3</error_code> <error_msg>Invalid parameters</error_msg> <param_missing> <param_name>api_key</param_name> </param_missing> <param_missing> <param_name>api_secret</param_name> </param_missing> </error>
This section describes the general process for using the API to post race results. There are variations you can make to this process depending on your needs. For example, you may use the API keys for a partner instead of authenticating a user with OAuth. This example assumes that you will download the registration id for each participant and map finishers to their registration id.
Once you have this completed, be sure to check out our API Methods for more advanced features:
RunSignup users can be authenticated by your application or website using OAuth and the RunSignup API. The RunSignup OAuth Integration Guide describes how to do this.