WebHooks

eb Hooks need only to be created when you want to use the Triggered Action feature (e.g. print a bib when new competitor is created) on participant changes.

Depending whether you work online or offline, your RR12 event needs to be configured slightly different.

Online

Our RemoteRedirect webservice provides a bridge between RR12 working online that can only access public web servers and RRExchange running locally.

Protocol is https and host is raceresult.remoteredirect.com: https://raceresult.remoteredirect.com

The following web hooks need to be configured in RR12 (Main Window - Access Rights/Simplae API - Web Hooks):

TypeURLFilterFields

New Participant

https://raceresult.remoteredirect.com/api/raceresult/newparticipant

ID;Bib;Lastname

Participant updated

https://raceresult.remoteredirect.com/api/raceresult/updateparticipant

ID;Bib;Lastname

RR12 Configuration when working online

Offline

When working offline (e.g. checking out the event and using the local race result Web Server, RRExchange acts a a server to receive web hooks.

Protocol is http (not https) and host is localhost:8181 (no www, take care with the :): http://localhost:8181

The following web hooks need to be configured in RR12 (Main Window - Access Rights/Simple API - Web Hooks):

TypeURLFilterFields

New Participant

http://localhost:8181/api/raceresult/newparticipant

ID;Bib;Lastname

Participant updated

http://localhost:8181/api/raceresult/updateparticipant

ID;Bib;Lastname

RR12 Configuration when working offline

Last updated