Build a Workout Accountability SMS Buddy with the Strava API, Twilio Functions,...

With gyms closed during quarantine, many people are trying to run or bike more outdoors (at a safe social distance from others, of course!) Strava is a popular social fitness app that helps users track and share outdoor workouts. Read on to learn how to build a quarantine workout accountability SMS system with the Strava API ,Twilio Functions, and the Twilio Serverless Toolkit .

Prerequisites

1. A Strava account - sign up here  if you don't have one already
2. A Twilio account - sign up for a free one here and receive an extra $10 if you upgrade through this link
3. A Twilio phone number with SMS capabilities -configure one here
4. Postman  (you could alternatively make cURL requests from the command line)

Setup the Strava API

In order to use the Strava API , you need to create an app. If you’re reading this, you likely already have a Strava account but if not go ahead and create one now from the  Prerequisites link above. Sign in to your Strava account and navigate to your API settings page . You can alternatively find that by selecting My API Application in the dropdown menu on the left of your regular account settings .

You should now see the “My API Application” page. Fill it out accordingly:

• Application name (I called mine Quarantine Accountability )
• Category ( social motivation,  perhaps?)
• Club (I left this blank as I'm not in a Strava club and it's not required)
• Website (I used my personal website, this can be anything)
• Application description ("maybe this will make me run more?")
• Authorization Callback Domain ( localhost )

Agree to Strava's API agreement and click Create. Yay! You have your first Strava application.

Make your first Strava API Request

The Strava API docs go over the endpoints you can use and the arguments they take. This post will start off hitting the endpoint to receive your personal statistics which requires two pieces of information for query string parameters:

1. Your numeric athlete ID is found by navigating to your Strava profile (click My Profile ) in the top right corner and look at the URL after /athletes .
    
2. Your Access Token, found in your API application settings . 

Open Postman and paste https://www.strava.com/api/v3/athletes/{your-athlete-ID}/stats into the URL bar, replacing {your-athlete-ID} with your ID from above (from your personal Strava page, not your API settings page.)

Underneath the URL bar, select Params .  Add a Key called access_token and its corresponding Value of your access Token from the last step.

Click the blue Send button to make a GET request and you should see something like this in Postman:

Nice! You just accessed your statistics in a nice JSON format. Feel free to play around with different Strava endpoints and see what other information you can access.

Strava Activity Webhook Authentication

Strava changed its API authorization process in 2018. The Access Token from above has scope:read which is insufficient to make a request to each endpoint. For example, to access any Activity webhook the scope must instead be activity:read . Let's make an Access Token that can hit an Activity webhook.

1. Grab your client ID from your Strava app settings. In a web browser tab, type into the URL bar https://www.strava.com/oauth/authorize?client_id=YOUR_CLIENT_ID&redirect_uri=http://localhost&response_type=code&scope=activity:read and click enter . You should see a screen like this:
2. Click Authorize. In the URL bar, copy the code as shown below. 
3. Now back in Postman, add https://www.strava.com/oauth/token in the Postman URL bar and add the following parameter keys and their corresponding values: client_id and client_secret whose values you can find in your Strava app settings, code with the code from step two, and grant_type whose value is authorization_code .

Make the POST request and you should receive some JSON like this:

With this new Access Token we can access the Strava Activities endpoint . To test the information we receive from this endpoint, make another Get request in Postman that looks something like this:

This returns details about the most recent Strava activity completed.

Now we can move on to making our Twilio app with the CLI and Functions to hold ourselves accountable for exercising.

Make and Test the Function Locally

Let’s write a function that uses the Strava API to compute the time and distance of our last activity, and wraps that information in TwiML. To debug our Function more easily, we'll use theServerless Toolkitdeveloped by my teammate Dominik . For more details on installation and project structure, check out the docs on how to develop and debug Twilio Functions locally .

The best way to work with the Serverless Toolkit is through the Twilio CLI. If you don't have the Twilio CLI installed yet, run the following commands to install it and the Serverless Toolkit:

npm install twilio-cli -g
twilio login
twilio plugins:install @twilio-labs/plugin-serverless

Afterwards create your new project by running:

twilio serverless:init twilio-function strava-demo
cd strava-demo
npm install got

const got = require('got');
exports.handler = async function (context, event, callback) {
  let twiml = new Twilio.twiml.MessagingResponse();
  try {
    const response = await got(
  `https://www.strava.com/api/v3/athlete/activities?per_page=1&access_token=${context.STRAVA_ACCESS_TOKEN}`
    );
    const data = JSON.parse(response.body);
    var distance = data[0].distance;
    //convert distance in meters to miles if activity distance is less than 1 mile
    if(!distance < 1609.34) {
        distance = Math.round(data[0].distance * 0.000621371192); //meters to miles
        distance = distance.toString().substring(0,6);
        distance += '-mile';
    }
    else {
        distance += '-meter';
    }
    const date = data[0].start_date;
    const prettyDate = date.substring(5,10); // month and day
    var time = data[0].moving_time;
    time = secondsToHrsMins(time);
    const activityType = data[0].type.toLowerCase();

   twiml.message(
     `{insert-your-name}'s last Strava workout was a ${distance} ${activityType} on ${prettyDate} in ${time} minutes. Encourage them to ${activityType} again soon.`
   );

    callback(null, twiml);
  } catch (error) {
    console.log(error);
    twiml.message("There was an error getting the data from the Strava API. Try again later or ping {your-name} directly to motivate them to get some fresh air today.");
    callback(null, twiml);
  }
};
function secondsToHrsMins(seconds) {
    var date = new Date(null);
    date.setSeconds(seconds); // specify value for SECONDS here
    return date.toISOString().substr(11, 8);  
}

Add your Access Token from the authentication portion as an environment variable in your Function's .env called STRAVA_ACCESS_TOKEN so others can't see it and use it, and check that the got module is listed as a dependency (not a devDependency) in your projects package.json , both files of which are in your root directory. Still in your root directory, run followed by npm start . You should see some local URLs you can test.

Going to localhost://3000/strava in the browser should display a page like this:

Configure our Function with a Twilio Phone Number

To open up our app to the web with a public-facing URL, run twilio serverless:deploy . You should see this at the bottom of your terminal:

Grab the Function URL corresponding to your app (here it has /strava ) and configure a Twilio phone number with it as shown below.

Click Save and now text anything to your Twilio phone number for a response like this one:

Warning: Strava Access Tokens expire after six hours. For more information on refreshing expired Access Tokens, check out this section of the Strava docs .

What's Next

You can access and play around with different JSON information with different Strava API endpoints . I don't know about you, but I feel like it's time to go for a run so people don't ask me why I haven't done so in a while. Let me know online or in the comments section what you're working on.

• Twitter: @lizziepika
• GitHub: elizabethsiegle
• Email:[email protected]

Authors

• Lizzie Siegle