Quick Links

Accepted file formats

All files adhering to the standards TCX and FIT formats will be parsed.

However, some rowing related parameters are not supported by TCX and FIT. Therefore, we are supporting the CSV format that is documented in the following link.

• Our standard rowing CSV file

Using this standard will guarantee that your user's data are accepted without complaints.

API related documentation

Registering an app

As a registered user, you can register an app.

• Self-service app link.

Authentication

Standard Oauth2 authentication. Get authorization code by pointing your user to the authorization URL. Exchange authorization code for an access token. When access token expires, use the refresh token to refresh it.

The POST call must have content-type: x-www-form-urlencoded. I set it this way to support the handy testing utility mentioned belower. However, I really would like to support application/json but with the current framework I cannot support both at the same time. Expect changes. Write to me if you want to be notified of changes.

• Authorization URL: https://rowsandall.com/rowers/o/authorize
• Access Token request: https://rowsandall.com/rowers/o/token/
• Access Token refresh: https://rowsandall.com/rowers/o/token/
• Handy utility for testing: http://django-oauth-toolkit.herokuapp.com/consumer/

API documentation

Once you have a registered app, you have gone through the authorization and have successfully obtained an access token, you can use it to place POST, GET and PUT requests.

The workout summary data and the stroke data are obtained and sent separately.

• API documentation (But refer to the below for stroke data.)
• Try out the workout summary API
• GET stroke data

You can only post stroke data to an existing workout with workout number {id}. If the workout already has stroke data, you will get a duplication error. This functionality will be expanded in the future to enable updating stroke data. Stroke data for workout {id} are posted to:

• https://rowsandall.com/rowers/api/workouts/{id}/strokedata

The payload is application/json data and looks as follows:

    {
  "distance": [5,12,19,27,35,43,51,59,67,75,82,90,100],
  "power": [112,221,511,673,744,754,754,749,729,729,726,709,707],
  "hr": [132,131,131,132,133,136,139,142,145,147,150,152,153],
  "pace": [145800,116400,88100,80400,77700,77400,77400,77600,78300,78300,78400,79000,79100],
  "spm": [11,41,56,59,55,48,48,48,48,48,48,48,49],
  "time": [0,2200,4599,7000,9599,12000,14400,16799,19400,21799,24200,26599,2900],
}
    

Mandatory data fields are:

• time: Time (milliseconds since workout start)
• distance: Distance (meters)
• pace: Pace (milliseconds per 500m)
• spm Stroke rate (strokes per minute)

Optional data fiels are:

• power: Power (Watt)
• drivelength: Drive length (meters)
• dragfactor: Drag factor
• drivetime: Drive time (ms)
• strokerecoverytime: Recovery time (ms)
• averagedriveforce: Average handle force (lbs)
• peakdriveforce: Peak handle force (lbs)
• lapidx: Lap identifier
• hr: Heart rate (beats per minute)

Consistency checks will be done and the stroke data will be refused if the mandatory data fields don't pass the checks. All mandatory data fields must have the same number of records. If an optional data field fails a test, its values are silently replaced by zeros.