1. RunSignup
  2. API
  3. Methods
  4. Post Manual Division Placements

Post Manual Division Placements

Post division placements to a results set. You should Disable Automatic Division Placement Calculations before using this method. You may want to Clear Division Placements beforehand if needed or if you need to reupload editing placements.

Each request can contain multiple placements, with each containing race_division_id, result_id, and division_placement. If a runner does not get a place in a division (e.g. they won the overall division), division_placement should be set to null.

Optionally, you can also specify manual division finisher counts using division_num_finishers. This allows you to override the automatically calculated “out of” count that appears in division placements (e.g., “1st out of 25”). If not provided, finisher counts will continue to be calculated automatically based on the actual number of results in each division. To clear a finisher count when using XML, send an empty element like <num_division_finishers></num_division_finishers>. For JSON, set the value to null.

You can also optionally specify the overall finisher count using overall_num_finishers. This allows you to override the automatically calculated total finisher count that appears in overall placements (e.g., “5th out of 1,250“). If not provided, the overall finisher count will continue to be calculated automatically based on the total number of results in the result set. To clear the overall finisher count when using XML, send an empty element like <overall_num_finishers></overall_num_finishers>. For JSON, set the value to null.

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

{
	"placements": [
		{
			"race_division_id": 123,
			"result_id": 123,
			"division_placement": 1
		},
		{
			"race_division_id": 123,
			"result_id": 456,
			"division_placement": 2
		}
	],
	"division_num_finishers": [
		{
			"race_division_id": 123,
			"num_division_finishers": 120
		}
	],
	"overall_num_finishers": 1250
}

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

<request>
	<placement>
		<race_division_id>123</race_division_id>
		<result_id>123</result_id>
		<division_placement>1</division_placement>
	</placement>
	<placement>
		<race_division_id>123</race_division_id>
		<result_id>456</result_id>
		<division_placement>2</division_placement>
	</placement>
	<division_num_finishers>
		<race_division_id>123</race_division_id>
		<num_division_finishers>120</num_division_finishers>
	</division_num_finishers>
	<overall_num_finishers>1250</overall_num_finishers>
</request>

URL

https://api.runsignup.com/rest/race/:race_id/results/manual-divisions-placements

HTTP Method

POST

Standard Parameters

Parameter HTTP Method Default Description Datatype
api_key GET API Key string
api_secret GET 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
Authorization HTTP Header Authorization Header. If using OAuth 2.0, fill this in with `Bearer <token>`. string
format GET xml Format of response. The default if not sent is `xml`, but `json` is preferred. 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. The default if not sent is `xml`, but `json` is preferred. 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.