If you're working with an external timing or scoring system — such as a chip timing system or an aquatics timing platform — you can push scores directly into Competition Corner in real time through a simple API connection.
If your external system does not support API delivery, see Importing Scores for a manual alternative.
Prerequisites
Before setting up the API connection, confirm the following:
Your external system is capable of delivering data over an API
The system can provide, at minimum, a participant ID and a result per entry
If scores are time-based, they must be formatted as HH:MM:SS.000
Expected Data Format
Below is an example of what a typical API payload looks like in JSON format:
json
[
{
"First Name": "Lexi",
"Last Name": "DeSaracho",
"Gender": "Female",
"Team Name": "",
"CompCornerID": "524658",
"CGID": "1236",
"Time": "00:13:37.2"
},
{
"First Name": "Allison",
"Last Name": "McClellan",
"Gender": "Female",
"Team Name": "",
"CompCornerID": "527182",
"CGID": "1245",
"Time": "00:13:59.1"
}
]
The two required fields are CompCornerID (the participant ID) and your result field (e.g., Time). Additional fields such as name, gender, and team are optional but recommended for easier troubleshooting.
Setting Up Your API Connection
Navigate to Scoring Setup and click the API Integration tab
Click + to add a new connection
Select the workout you want to map scores to
Map your data points — match the fields from your external system to the corresponding fields in Competition Corner
Set the polling frequency — how often Competition Corner should pull data from the source API
Testing Your Connection
⚠️ Test thoroughly before going live. Your timing provider should be able to run a simulation to validate the connection end-to-end.
A quick way to test within Competition Corner:
Duplicate an existing workout
Apply the same API settings to the duplicate
Confirm that scores are being processed correctly
Delete the test workout once validated
Do not skip this step - Scoring issues during a live event are extremely stressful to resolve — athletes are finishing, leaderboards are updating, and the clock doesn't stop. Trying to diagnose and fix a broken API connection while simultaneously keeping up with an event in progress can quickly become overwhelming. A few minutes of testing before your event starts can save hours of firefighting on competition day.
Score Amendments
Once a score has been imported into Competition Corner, the API will skip that record on all subsequent syncs. This means any score corrections after the initial import must be made directly within Competition Corner — not at the source system.
This behavior is intentional. It protects manually reviewed scores from being overwritten by the source system in cases where a result has been adjusted following an appeal or official review.
The workflow for score amendments is:
An athlete submits an appeal or a scoring error is identified
The score is reviewed and a correction is determined
The corrected score is updated directly in Competition Corner
The API will recognize the record has already been imported and will not overwrite the corrected score
Considerations for Team Events
If you are using chip timing for team events, you have two approaches:
Option 1 — One chip per team Assign a single chip to the team. The score recorded by that chip is submitted directly as the team's result.
Option 2 — One chip per team member If every team member is chipped individually, Competition Corner can automatically aggregate individual member scores into a team score. To enable this, your source system must include the Teammate ID with each returned data record so Competition Corner can correctly associate each score to the right team.
Additionally, ensure all team member scores are accounted. A partial team score may appear in the leaderboard before all members have finished, which can cause incorrect interim standings.