Post User Submitted Virtual Results

Post a user submitted race result to the API.

The individual_result_set_id parameter is required if you have multiple result sets for an event. If not set, the existing result set will be used if it exists. Otherwise, a new result set will be automatically created.

The event_id must be for a Virtual Event.

Format for clock_time is hhh:mm:ss.s, but you can also use the strings “DQ”, “DNS”, “DNF”, or “DNQ”.


The request parameter depends on request_format.

For 'json', the request should be an object with a 'virtual_results' property, which is an array. Each result will be an object with field values being stored as the property with that field name. You must include either registration_id or bib_num. If registration_id is set and bib_num is not set or does not match the bib number associated with registration_id, the bib number associated with registration_id will be used for the result. If bib_num is set and registration_id is not set, the registration id associated with bib_num will be used for the result. The tally_value is optional. If not set, it will not be changed. If set, but empty or null, it will be cleared. If elevation gain is allowed for the virtual event, then elevation_gain_in_mm is required. Otherwise elevation gain will not be set. An example is below.

{
	"virtual_results": [{
			"bib_num": 123,
			"clock_time": "00:17:00.1",
			"tally_value": null,
			"registration_id": 3210,
			"elevation_gain_in_mm": 1200
		},
		{
			"bib_num": 456,
			"clock_time": "00:17:00.2",
			"tally_value": 1.75,
			"registration_id": 3211,
			"elevation_gain_in_mm": 12000
		}
	]
}

Response

{
	"virtual_results": [
		{
			"registration_id": 8106676,
			"bib_num": 1,
			"results_received_ts": 1586571360,
			"individual_result_set_id": 17030,
			"submitted_time_in_ms": 1020000,
			"elevation_gain_in_mm": 1200,
			"result_approval_ts": null
		}
	]
}

For 'xml', the request should look like the example below.

<request>
	<virtual_result>
		<bib_num>123</bib_num>
		<clock_time>00:17:00.1</clock_time>
		<tally_value></tally_value>
		<registration_id>3210</registration_id>
	</virtual_result>
	<virtual_result>
		<bib_num>987</bib_num>
		<clock_time>00:17:02.5</clock_time>
		<tally_value>1.75</tally_value>
		<registration_id>3211</registration_id>
	</virtual_result>
</request>

Response

<event_individual_results_user_upload>
    <virtual_results>
        <virtual_result>
            <registration_id>2645519</registration_id>
            <bib_num>1</bib_num>
            <results_received_ts>1586572952</results_received_ts>
            <individual_result_set_id>895</individual_result_set_id>
            <submitted_time_in_ms>1020500</submitted_time_in_ms>
            <result_approval_ts></result_approval_ts>
        </virtual_result>
    </virtual_results>
</event_individual_results_user_upload>

URL

https://runsignup.com/rest/race/:race_id/results/user-results

HTTP Method

POST

Standard Parameters

Parameter HTTP Method Default Description Datatype
api_key GET API Key string
api_secret GET API Secret string
tmp_key GET Temporary API Key from login API call. This should NOT be used in combination with API Key. string
tmp_secret GET Temporary API Secret from login API call. This should NOT be used in combination with API Secret. string
rsu_api_key GET API v2 key. If used, you must send the API secret in an HTTP header named X-RSU-API-SECRET. string
sp_api_key GET Super partner API key. If used, you must send the API secret in an HTTP header named X-RSU-API-SECRET. string
X-RSU-API-SECRET HTTP Header API v2 or super partner secret. string
format GET xml Format of response. format

Parameters

Parameter HTTP Method Default Description Datatype
race_id
Required
POST ID of race. uint
event_id
Required
POST ID of event. uint
individual_result_set_id POST ID of result set. uint
request_format POST xml Format of request. format
request
Required
POST Request in proper format. string

If you continue to use this site, you consent to use all cookies. We use cookies to offer you a better browsing experience. Read how we use cookies and how you can control them by visiting our Privacy Policy.

If you continue to use this site, you consent to use all cookies.