Update the URL for blades to use the RegattaCentral CDN.
Change the Entry.entry_code to be camelCase as Entry.entryCode.
Set the event's default race type to be that of the regatta's race type.
Add the bow number to the entry
Remove null orgContact records
Add Coastal race type
Add the Venue structure to the general regatta information retrieval
Resolves issue causing a "Bad Request" when data upload contains an athlete without an existing athlete_id.
The API now follows the same logic as the main website in regards to hiding lineups. "Bulk" downloads
will still load all entries regardless of the lineup deadline model and/or entrant's specifications.
For regattas with authorized access to Oarspotter.com blades, a URL is now supplied
with each Organization that points to the blade design.
For regattas utilizing "Guaranteed Entry Codes", these entry codes are now provided
with each entry.
For regattas which post only links to their results, the regatta structure now includes a list
of URLs for those documents.
Added a number of endpoints for retrieving regatta data.
See the list under "Retrieving General Regatta Information".
Payment data has been turned off by default pending data query optimization for large regattas. It can be enabled by adding
the query parameter "payments=true" to the bulk retrieve. For example:
Gzip compression support - Gzip compression is now supported for both uploads and downloads of data.
To receive a Gzip response, the Http Header "Accept-Encoding" must contain "gzip". To upload Gzipped data, the Http Header must
include "Content-Encoding" with a value of "gzip". If you do not specify these headers, then you will
continue to receive your data in an uncompressed format.
Payment Data - Each organizations' orgContacts may also include a "paymentSummary" structure. This data is reported the same way that the
staff Payment Summery report is. To assist in displaying these values, the regatta structure now also includes the
The structure contains:
Governing Body Support - If your regatta is sanctioned by a governing body (this currently applies only to USRowing sanctioned regattas)
then additional information will be provided in the bulk download:
The regatta will contain the "governingBody". This organization structure contains the information about the governing body.
The orgParticipants and orgContacts for this organization structure will be empty.
Each participant will have a "governingDetails" structure which contains the member ID and a list of requirements.
This list denotes the requirement (ie "waiver") and a boolean that the participant is compliant or not. Other requirements
such as photo release and anti-doping requirements may be added to this list of requirements in the future.
Ensure that coach's organizations are in the organization list if they are representing a different organization than the entry
Bulk download SQL optimization to improve performance
Ensure that all organizations are in the organization list
Do not include the entry organization it is being represent by the entry
Add event.defaultHandicapAlgorithm [0..1]
Add event.maxAlternates [0..1]
Populate handicap fields
Add entry.waitListPriority [0..1] for waitlisted entries