Flutter

If you do not need to access the mobile-only integrations , there is no reason to use Terra mobile SDKs!

If you need to access Terra's Health & Fitness API, it is only secure to do so from your server backend and send the desired data to your mobile frontend.

Never expose your API key on the client side unless you are simply testing

Setup

Install the terra-react package using npm (flutter pub add terra_flutter_bridge), and follow the respective guides below based on the platforms you want to access

iOS Setup - Apple Health

Using XCode, open the .xcodeproj for the app in the /ios directory of your project

Summary:

1. Add https://github.com/tryterra/TerraiOS as a package dependency

2. Add Capabilities:

   1. Healthkit > Healthkit Background Delivery

   2. Background Modes > Background processing

   3. Background modes > Background fetch

3. In your info.plist, add:

   1. Privacy - Health Share Usage Description: custom text shown in the Apple Health permission screen

   2. Permitted background task scheduler: co.tryterra.data.post.request

Background Delivery setup (iOS)

RunsetUpBackgroundDelivery in your AppDelegate's didFinishLaunchingWithOptions function

This will ensure you get updates for the user's Apple Health data automatically sent to your destination.

Data will

• still be sent even if your app is exited/killed completely

• only be sent if the device is unlocked

#import "AppDelegate.h"

#import <React/RCTBundleURLProvider.h>
#import <TerraiOS/TerraiOS-Swift.h>

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  self.moduleName = @"AwesomeProject";
  // You can add your custom initial props in the dictionary below.
  // They will be passed down to the ViewController used by React Native.
  self.initialProps = @{};
  [Terra setUpBackgroundDelivery];
  return [super application:application didFinishLaunchingWithOptions:launchOptions];
}

Android - Health Connect

Follow the instructions below within the /android directory of your project

Initialize the SDK

First, initialize the TerraManager class at the top level of the app.

Terra initialization

Terra should be initialized every time your app is opened.

This is a necessary prerequisite for other SDK functions to run as expected

To do this, run the Terra manager initialization function as below:

import 'package:flutter/material.dart';
import 'package:terra_flutter_bridge/terra_flutter_bridge.dart';

void main() async {
  // Ensure that Flutter bindings are initialized
  WidgetsFlutterBinding.ensureInitialized();

  // Initialize Terra once when the app starts
  await _initializeTerra();

  // Launch your app thereafter
  runApp(Container());  // Empty container or basic widget if needed
}

Future<void> _initializeTerra() async {
  try {
    String devID = 'YOUR_DEV_ID';
    String referenceID = 'YOUR_REFERENCE_ID';

    SuccessMessage? result = await initTerra(devID, referenceID);

    if (result?.success == true) {
      print('Terra initialized successfully');
    } else {
      print('Initialization failed: ${result?.error}');
    }
  } catch (error) {
    print('Error during Terra initialization: $error');
  }
}

Terra is thereafter ready to be used with other functions

Connect to Apple Health/Samsung Health

Once Terra is initialized, you can create a connection.

Run the initConnection function with Connections.APPLE or Connections.SAMSUNG to have the Apple Health or Health Connect permission screen pop up.

initConnection only needs to be run a single time.

Apple Health & Health Connect prohibit the permission popup to appear more than once for any given permission, so calling initConnection more than once will result in no action at all

The only case where it would re-appear is if:

• you call initConnection with an expanded set of customPermissions

• the app is deleted & reinstalled.

try {
  // Example token received from your backend
  String token = 'example_token';
  
  // Define connection type and custom permissions
  Connection connection = Connection.APPLE;
  List<CustomPermission> customPermissions = [];  // Leave empty to default to all permissions
  bool schedulerOn = true;  // Enables background delivery

  // Initialize the connection
  SuccessMessage? successMessage = await initConnection(
    connection,       // The type of connection (e.g., Apple Health)
    token,            // Token received from backend
    schedulerOn,      // Enables background delivery
    customPermissions // Empty list for custom permissions
  );

  if (successMessage?.success == true) {
    print('Connection successful!');
  } else {
    print('Connection failed: ${successMessage?.error}');
  }
} catch (error) {
  print('Connection failed with error: $error');
}

customPermissions

customPermissions is used to customize the permissions list shown in the Apple Health/Health Connect popup when calling initConnection. When empty, it defaults to all available permissions

🚧 Webviews & HealthKit permissions screen

HealthKit implements the permissions popup as a webview

If your app is also based on a webview, you will need to interrupt your webview, call initConnection, then upon completion re-open your webview

token

token is a single-use token created to ensure the authentication endpoint for creating a (and connecting the SDK to Terra's servers) does not get abused.

In order to generate it, place the call below on your server, and provide it to your client side using your own logic.

Testing & developing

During the development phase, it it acceptable to place this call on the client side, exposing your API key in your mobile app.

For a production implementation, DO NOT expose your API key this way, and make sure to only make this call from your backend

Generates an authentication token for the Terra mobile SDKs

Creates a token to be used with initConnection() functions in the Terra mobile SDKs in order to create a user record for Apple Health or Samsung Health (or equivalent)

post

/auth/generateAuthToken

Authorizations

apiKeyAuthdevIdAuth

Header parameters

dev-idstringrequired

your developer ID

Example: testingTerra

x-api-keystringrequired

your API key

Example: OtHJok60oQmT8zhnUWc4SWBJI7ztPTs88C0gOsJJ

Responses

application/json

application/json

cURL

JavaScript

Python

HTTP

cURL

curl -L \
  --request POST \
  --url 'https://api.tryterra.co/v2/auth/generateAuthToken' \
  --header 'x-api-key: text' \
  --header 'dev-id: text'

200

404

200

{
    "status": "success",
    "token": "250c68b9c21b78e40e7a3285a2d538d3bc24aabd3b4c76a782fb0a571ca4501d",
    "expires_in": 180
}

200

Validate the Connection

To ensure a connection is still valid on the client side, use the getUserId method. This function is synchronous and returns the user_id right away or null if none exists.

static Future<UserId?> getUserId(Connection connection) async

Always use this method right after initializing Terra to see if the connection still exists,

• if you expect the connection to exist, but getUserId returns null, call initConnection to re-establish it. No permission screen will be shown again and the user flow will be unaffected
• if it is expected for the connection to no longer exist, you may allow the user to re-connect Apple Health if they so choose (you'd then call initConnection as before, but no permission screen would be shown)
• if the connection exists, all is good! 🎉 keep vibing along

Disconnecting a user

In order to disconnect an Apple Health user, you may use the same endpoint as for Web API-based integrations, called from your backend

Historical Data retrieval

You can request for historical data using one of the data retrieval functions.

You may set toWebhook to false if you wish for the callback function to return the data payload on the client side.

try {
  // Example connection type and dates
  Connection connection = Connection.APPLE;  // Assuming Connection is an enum with APPLE
  DateTime startDate = DateTime.now().subtract(Duration(days: 1));  // Replace with actual start date
  DateTime endDate = DateTime.now();                                // Replace with actual end date
  
  // Optionally, send data to webhook or not
  bool toWebhook = false;  // Set to false to receive the data in the response

  // Call the getDaily function
  DataMessage? dataMessage = await getDaily(connection, startDate, endDate, toWebhook: toWebhook);

  // Handle the response based on the structure of DataMessage
  if (dataMessage?.success == true) {
    if (dataMessage?.data != null) {
      print('Daily data: ${dataMessage?.data}');
    } else {
      print('Failed to unpack data');
    }
  } else {
    print('Request failed with error: ${dataMessage?.error}');
  }

} catch (error) {
  // Handle failure (network error, etc.)
  print('Failed to get daily data: $error');
}

Check out the Flutter SDK reference for details about all the functions in the SDK

Writing Planned Workouts (Apple-Only)

Planned Workouts are only available for APPLE, and on iOS 17 and above

Overview

Writing planned workouts allows you to create a workout plan for the user (such as those commonly used with Zwift)

This will typically look like the following example:

Example workout from https://whatsonzwift.com/workouts/baby-on-board

Planned workouts consist of a series of steps. Each step has:

• Completion criteria (called duration for all intents and purposes). For example:

  • distance (keep going until you cover 500m),

  • energy expenditure (keep going until you burn 200 kcal)

  • heart rate threshold (keep going until your heart rate reaches above 150 bpm)

  • etc..

• A target to be maintained

  • heart rate (maintain heart rate between certain bounds)

  • speed (maintain speed between certain bounds)

  • grade (inclination above a certain threshold)

  • etc...

• An associated intensity label

  • Warmup

  • Active

  • Cooldown

  • etc..

• An exercise type

  • Running

  • Cycling

  • Deadlifting

  • etc...

• A series of sub-steps

These modalities allow any workout to be described in a series of defined steps for each of its segments.

Once written, a planned workout will be available in the user's Workout app on their Apple Watch. They will then be able to follow the workout and receive guidance throughout each step.

Usage

In order to write a workout for the user to follow on their Apple Watch, use the postPlannedWorkout function as below, with the instance of terra you created above

import 'package:terra_flutter/terra_flutter.dart';

void sendPlannedWorkout() async {
  // Create a planned workout payload
  TerraPlannedWorkout plannedWorkout = TerraPlannedWorkout(
    metadata: TerraPlannedWorkoutMetaData(
      id: "unique-workout-id",
      name: "Morning Run",
      type: TerraActivityType.RUNNING,
      planned_date: DateTime.now().toIso8601String(),
      estimated_duration_seconds: 3600, // Estimated 1 hour workout
    ),
    steps: [
      PlannedWorkoutStep(
        order: 1,
        type: PlannedWorkoutStepType.STEP,
        name: "Warm-up",
        durations: [PlannedWorkoutStepDuration.Time(
          TimePlannedWorkoutStepDuration(seconds: 600)
        )], // 10-minute warm-up
        targets: [PlannedWorkoutStepTarget.HeartRate(
          HRPlannedWorkoutStepTarget(hr_bpm_low: 120, hr_bpm_high: 140)
        )]
      ),
      PlannedWorkoutStep(
        order: 2,
        type: PlannedWorkoutStepType.STEP,
        name: "Run",
        durations: [PlannedWorkoutStepDuration.Time(
          TimePlannedWorkoutStepDuration(seconds: 3000)
        )], // 50-minute run
        targets: [PlannedWorkoutStepTarget.Speed(
          SpeedPlannedWorkoutStepTarget(speed_meters_per_second: 3.0)
        )]
      )
    ],
  );

  // Send the workout to Apple Health
  SuccessMessage? response = await TerraFlutter.postPlannedWorkout(
    Connection.APPLE, 
    plannedWorkout
  );

  // Check if the operation was successful
  if (response?.success == true) {
    print("Planned workout successfully posted.");
  } else {
    print("Failed to post the planned workout: ${response?.error}");
  }
}