RACE RESULT 14 can send webhooks upon certain triggers, these are predominantly used to ensure the synchronization of data between 2 separate data stores, for example if you are using your own registration platform and want to ensure participant data is updated if it is changed in the Event File. 

Webhooks are configured under Basic Settings ⇒ Access Rights / Simple API.

Each webhook needs to define the trigger, the destination URL, and for certain triggers a filter and fields can be defined. 

When setup and activated the webhooks will automatically be sent according to the triggers defined, there is no time limit to how long webhooks will be activated for. 

All webhooks are sent as a POST request with data in the POST body as JSON, by default the body will always contain Event ID, Webhook ID, Timestamp, additional values depend on the trigger being used. 

A call is considered successfully sent if a response code <500 is received, even if the status code is an error code it is still considered received by the destination. If a call is unsuccessful then the server will attempt to resend it with an increased delay between or until the Server queue limit is reached at which point the message will be dropped. 

Webhooks are sent by the SES which is running the event file, if you are timing offline, even with online forwarding enabled, the webhooks will only be sent by your local SES. 

Triggers

New Participant

A call will be sent when a new participant is added, this can be either through import participants, online registration, on-site registration or directly through the participants window. 

A filter can be applied to only send the webhook if a certain filter is true, for example if a participant has selected a specific option during registration. 

The post body can also include any fields which are defined as a list of semi-colon separated values. 

Participant Update

Similar to the new participant trigger the participant update will send whenever the data fields of a participant record are changed, this will not be triggered by changes to Splits, Results calculations or User-Defined Fields.

A filter can also be applied to participant updates and the post body can be configured to include fields as well. 

New Raw Data

The new raw data trigger will be sent whenever a new raw data record is added, the record is linked to a participant record so you can optionally define a filter and fields to be included in the POST body. 

When using the New Raw Data it is recommended to link the filter to a specific result or the Finish result, for example - only send the webhook if the participant is Finished. Any calculations which depend on the raw data record will be completed first so it will send even if that time is used for the specific result you are looking at. 

Settings Changed

This applies to any event file settings which are changed, this includes for example all Event, Chip Timing and Scoring settings, updates to Output Lists, my.rr settings and more.

Since the settings apply to the Event file and not a participant record it cannot be filtered or include additional fields. The Post body will include the ModJobID in the Values field to allow you to track the changes. 

The ModJob ID is an integer which represents the last calculation cycle run by the SES. Whenever something is changed in an event file a unique job is run which calculates what should be updated in the database. This ID will increase for every change no matter how big or small. 

All Changes

All changes means any change to the event file. 

Since the all changes applies to the Event file and not a participant record it cannot be filtered or include additional fields. The Post body will include the ModJobID in the Values field to allow you to track the changes.