API

revSPORT currently has two APIs available to assist clubs in the running of their club and events

More information and expression of interest are below

Membership API

The Membership API will aim to integrate a Club’s third-party membership system with their revSPORT portal.

Practical applications of the API will be:

A Club’s third-party system will query revSPORT to check or provide a member’s Australian Sailing number.
When a member is entered into the Club’s third-party system, they can then be automatically added to their revSPORT portal – hence being an active club member and be covered by the Australian Sailing personal accident insurance.
In cases where a SailPass is purchased in a third-party system, that information can be automatically transferred to revSPORT and a SailPass record will be created, once again ensuring the participant/member is covered by the personal accident insurance.

How does the API work?

What are the benefits

Successful application of an API between revSPORT and a club’s third-party system will reduce the administration required to maintain two systems, decrease duplicate records, ensure clean and current data is in both systems and accurate and instant record of membership numbers.

Member endpoint API

The member endpoint API allows a third party system to query the Australian Sailing Number checker to vertify the validity of an Australian Sailing Number.

In order to access either API, you will need to follow the process outlined below, ensuring;

Club approval from club CEO, GM, Commodore or President
Secured the assistance of your 3rd party system developer

The Process

Step 1

Complete online expression of interest

Click here to complete the Australian Sailing API Expression of Interest

Step 2

Australian Sailing will provide the club with the following documentation:
     Australian Sailing Club Integration Agreement
     revSPORT API Usage Agreement
     API Documentation

Step 3

Introduction with revSPORT + 3rd Party System + Club

During this meeting, the 3rd party system is able to ask any questions about the API workflow

Step 4

Agreements are signed and returned to Australian Sailing

Access to API key is provided

Step 5

3rd party system implements the API and carries out testing

Support is provided directly to the 3rd party from revSPORT until implementation is complete.

Questions?

Australian Sailing - Digital Platform onlineservices@sailing.org.au

Frequently Asked Questions

What fields are required?

The below fields are required:

Field	Required by AS	Required by revSPORT
AS Number
First Name
Last Name
DOB
Gender
Post Code
State
Country
Email address

Other fields are optional and can be chosen by clubs and configured by your third party.

What does Australian Sailing do with this data?

The main reason for AS collecting personal information is so that we can carry out our functions, including to provide products and services and enable participation in activities and events of AS, its affiliates and clubs. Other reasons for collecting personal information include:

· To provide you with your personal accident insurance cover (only valid for financial members of affiliated clubs when registered in the database);

· It proves compliance with rule 46 (helming or crewing in a race)

· To send you relevant sailing information and updates;

· To communicate directly with you when necessary

· Statistical analysis- ie gender, Date of Birth and postcode is important data that helps us identify trends and understand the dynamics of the sport.

· Reporting to Government

· Record qualifications and levels of accreditation

Is it two way or one way syncing?

There are both inbound and outbound APIs available.

For the most effective implementation, two way synchronisation will occur and will be configured by your 3^rd party system.