Set up splits for a result set. The splits posted will completely replace existing splits. You can specify a 'split_id' with each split to indicate that an existing split should be edited. The splits should be listed in the order they should be displayed in.
The 'pace_type' field can be:
The 'approx_percent_time_complete' field indicates the approximate percent of the race that has been completed in terms of time. This can be used with result notifications to estimate finishing times. For running races, this is typically the percent of the distance completed. For example, the 5 mile split in a 10 mile race would be 50%. For triathlons, you can leave it blank or use average times for each segment of the race to pick a percentage.
For JSON, the request should look like the example below.
{ "result_set_splits": [ { "split_id": null, "split_name": "3 Mile", "split_distance": 3, "split_distance_units": "M", "pace_type": "T", "approx_percent_time_complete": 30, "include_split_place": "F" }, { "split_id": null, "split_name": "5 Mile", "split_distance": 5, "split_distance_units": "M", "pace_type": "T", "approx_percent_time_complete": 50, "include_split_place": "F" }, { "split_id": null, "split_name": "7 Mile", "split_distance": 7, "split_distance_units": "M", "pace_type": "T", "approx_percent_time_complete": 70, "include_split_place": "F" } ] }
For XML, the request should look like the example below.
<?xml version="1.0" encoding="utf-8" ?> <result_set_splits> <result_set_split> <split_id></split_id> <split_name>3 Mile</split_name> <split_distance>3</split_distance> <split_distance_units>M</split_distance_units> <pace_type>T</pace_type> <approx_percent_time_complete>30</approx_percent_time_complete> <include_split_place>F</include_split_place> </result_set_split> <result_set_split> <split_id></split_id> <split_name>5 Mile</split_name> <split_distance>5</split_distance> <split_distance_units>M</split_distance_units> <pace_type>T</pace_type> <approx_percent_time_complete>50</approx_percent_time_complete> <include_split_place>F</include_split_place> </result_set_split> <result_set_split> <split_id></split_id> <split_name>7 Mile</split_name> <split_distance>7</split_distance> <split_distance_units>M</split_distance_units> <pace_type>T</pace_type> <approx_percent_time_complete>70</approx_percent_time_complete> <include_split_place>F</include_split_place> </result_set_split> </result_set_splits>
For CSV, the request should look like the example below.
split_id,split_name,split_distance,split_distance_units,pace_type,approx_percent_time_complete,include_split_place ,"3 Mile",3,M,T,30,F ,"5 Mile",5,M,T,50,F ,"7 Mile",7,M,T,70,F
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. The default if not sent is `xml`, but `json` is preferred. | format |
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 |