ClawHub

Strong Skill

Data & APIs

Interact with the Strong v6 workout tracker REST API — login, list exercises, fetch workout logs and templates, manage folders, tags, measurements, and widgets. Use when the user asks about their Strong app workouts, exercises, or training data.

Install

openclaw skills install strong-app

Strong Workout Tracker (v6 API)

Unofficial REST API for the Strong workout tracking app (v6+). All API interaction goes through the CLI dispatcher at scripts/strong_runner.py.

Warning: This API is reverse-engineered and unofficial. Use at your own risk.

Environment Variables

VariableDescription
STRONG_USERNAMEStrong account username or email
STRONG_PASSWORDStrong account password

Both must be set before running any command. The CLI reads them automatically.

Runner

All commands are invoked via:

python3 scripts/strong_runner.py <command> [--param value ...]

Every command authenticates automatically (login is handled internally), prints JSON to stdout, and exits. No manual token management is needed.

Workflow

  1. Pick the appropriate subcommand from the list below.
  2. Run it — authentication and token handling happen inside the runner.
  3. All collection responses use HAL format with _links, _embedded, and total.

1. Login

Authenticate and return tokens. Rarely needed directly — all other commands log in automatically.

python3 scripts/strong_runner.py login

Output: { "accessToken": "eyJ...", "refreshToken": "kf3Z...", "userId": "uuid" }

2. Refresh Token

Renew an expired access token without re-entering credentials.

python3 scripts/strong_runner.py refresh_token

Output: { "accessToken": "eyJ...", "refreshToken": "...", "expiresIn": 1200, "userId": "uuid" }

3. Get User Profile

Fetch the authenticated user's profile, preferences, and purchases.

python3 scripts/strong_runner.py get_profile

Response keys: id, created, lastChanged, username, email, emailVerified, name, goal, preferences, purchases, legacyPurchase, legacyGoals, startHistoryFromDate, firstWeekDay, availableLogins, migrated.

4. List Exercises (Measurements)

Fetch all exercises in the user's library.

python3 scripts/strong_runner.py list_exercises

Response (HAL):

{
  "_links": { "self": {...} },
  "_embedded": {
    "measurement": [
      {
        "id": "uuid",
        "created": "ISO8601",
        "lastChanged": "ISO8601",
        "name": { "custom": "Bench Press (Barbell)" },
        "instructions": { "custom": "..." },
        "media": [],
        "cellTypeConfigs": [{ "cellType": "...", "mandatory": true }],
        "measurementType": "EXERCISE"
      }
    ]
  },
  "total": 360
}

5. Get Single Exercise

python3 scripts/strong_runner.py get_exercise --measurement_id <uuid>
ParameterRequiredDescription
--measurement_idYesExercise/measurement UUID

6. List Workout Templates

Fetch all workout templates (routines).

python3 scripts/strong_runner.py list_templates

Response (HAL):

{
  "_embedded": {
    "template": [
      {
        "id": "uuid",
        "created": "ISO8601",
        "lastChanged": "ISO8601",
        "name": { "custom": "Push Day" },
        "access": "PRIVATE",
        "logType": "TEMPLATE",
        "_embedded": {
          "cellSetGroup": [
            { "id": "uuid", "cellSets": [...] }
          ]
        }
      }
    ]
  },
  "total": 75
}

7. Get Single Template

python3 scripts/strong_runner.py get_template --template_id <uuid>
ParameterRequiredDescription
--template_idYesTemplate UUID

Response keys: id, created, lastChanged, name, access, logType, _embedded.cellSetGroup[] (each with id, cellSets[]).

8. List Workout Logs

Fetch all completed workout sessions.

python3 scripts/strong_runner.py list_logs

Response (HAL):

{
  "_embedded": {
    "log": [
      {
        "id": "uuid",
        "created": "ISO8601",
        "lastChanged": "ISO8601",
        "name": { "custom": "Push Day" },
        "access": "PUBLIC",
        "startDate": "ISO8601",
        "endDate": "ISO8601",
        "logType": "WORKOUT",
        "_embedded": {
          "cellSetGroup": [
            { "id": "uuid", "cellSets": [...] }
          ]
        }
      }
    ]
  },
  "total": 552
}

9. Get Single Log

Fetch a single workout log. Pass --include_measurement to embed exercise data.

python3 scripts/strong_runner.py get_log --log_id <uuid>
python3 scripts/strong_runner.py get_log --log_id <uuid> --include_measurement
ParameterRequiredDescription
--log_idYesLog UUID
--include_measurementNoInclude exercise/measurement data in the response

Response keys: id, created, lastChanged, name, access, startDate, endDate, logType, _embedded.cellSetGroup[] (each with id, cellSets[], _embedded.cellSet[]).

10. List Folders

Fetch workout template folders.

python3 scripts/strong_runner.py list_folders

Response (HAL): _embedded.folder[] with keys: id, created, lastChanged, name, index.

11. List Tags

Fetch exercise tags/categories.

python3 scripts/strong_runner.py list_tags

Response (HAL): _embedded.tag[] with keys: id, created, name, color, isGlobal.

12. List Widgets

Fetch dashboard widget configuration.

python3 scripts/strong_runner.py list_widgets

Response (HAL): _embedded.widget[] with keys: id, created, lastChanged, index, widgetType, parameters.

13. Share a Template

Generate a shareable link for a workout template.

python3 scripts/strong_runner.py share_template --template_id <uuid>
ParameterRequiredDescription
--template_idYesTemplate UUID

14. Share a Workout Log

Generate a shareable link for a workout log.

python3 scripts/strong_runner.py share_log --log_id <uuid>
ParameterRequiredDescription
--log_idYesLog UUID

15. Get Shared Link

Retrieve a shared template or log by its link ID.

python3 scripts/strong_runner.py get_shared_link --link_id <id>
ParameterRequiredDescription
--link_idYesShared link ID

16. Get Log at Date

Fetch workout logs whose startDate falls on a specific date. Client-side filter over list_logs.

python3 scripts/strong_runner.py get_log_at_date --date 2025-03-15
python3 scripts/strong_runner.py get_log_at_date --date 2025-03-15T14:30:00+01:00
ParameterRequiredDescription
--dateYesTarget date (YYYY-MM-DD or ISO-8601 timestamp)

Response (HAL): _embedded.log[] — only logs matching the given calendar date.

17. Get Logs in Range

Fetch workout logs between two dates (inclusive). Client-side filter over list_logs.

python3 scripts/strong_runner.py get_logs_in_range --from 2025-01-01 --to 2025-03-31
ParameterRequiredDescription
--fromYesStart date (YYYY-MM-DD or ISO-8601)
--toYesEnd date (YYYY-MM-DD or ISO-8601)

Response (HAL): _embedded.log[] — logs sorted by startDate, within the range.

18. Get Latest Log

Return the single most recent workout log by startDate. Client-side filter over list_logs.

python3 scripts/strong_runner.py get_latest_log

Response: A single log object (not wrapped in _embedded).

19. Search Logs by Name

Search workout logs by name using a case-insensitive substring match. Client-side filter over list_logs.

python3 scripts/strong_runner.py search_logs_by_name --name "push day"
ParameterRequiredDescription
--nameYesSubstring to match against log names

Response (HAL): _embedded.log[] — matching logs.

20. Search Exercises by Name

Search exercises by name using a case-insensitive substring match. Client-side filter over list_exercises.

python3 scripts/strong_runner.py search_exercises_by_name --name "bench press"
ParameterRequiredDescription
--nameYesSubstring to match against exercise names

Response (HAL): _embedded.measurement[] — matching exercises.

21. Get Exercise History

Return all workout logs that contain a specific exercise (by measurement ID). Client-side filter over list_logs.

python3 scripts/strong_runner.py get_exercise_history --measurement_id <uuid>
ParameterRequiredDescription
--measurement_idYesExercise/measurement UUID to search for

Response (HAL): _embedded.log[] — logs containing the exercise, sorted by startDate.

External endpoints

EndpointPurpose
https://back.strong.app/auth/loginAuthenticate and obtain JWT tokens
https://back.strong.app/auth/login/refreshRefresh an expired access token
https://back.strong.app/api/users/{userId}User profile
https://back.strong.app/api/users/{userId}/measurementsExercises (measurements)
https://back.strong.app/api/users/{userId}/templatesWorkout templates
https://back.strong.app/api/users/{userId}/logsWorkout logs
https://back.strong.app/api/users/{userId}/foldersTemplate folders
https://back.strong.app/api/users/{userId}/tagsExercise tags
https://back.strong.app/api/users/{userId}/widgetsDashboard widgets
https://back.strong.app/api/links/{linkId}Shared links

No other external endpoints are contacted.

Security and privacy

  • Credentials are read exclusively from STRONG_USERNAME and STRONG_PASSWORD environment variables and are never logged, cached, or written to disk.
  • Tokens (JWT access and refresh) are held in memory only for the duration of a single invocation and are never persisted.
  • All traffic uses HTTPS only to back.strong.app.
  • The runner script (scripts/strong_runner.py) is pure Python using only the standard library — no shell expansion or interpolation of user input occurs.
  • No local files are read or written.

Model invocation note

The agent should invoke this skill whenever the user asks about their Strong app workouts, exercises, templates, workout history, tags, folders, or training data. The agent should call login implicitly before any data-fetching command and never expose raw tokens to the user. Prefer list_logs and list_templates for broad queries, and get_log --log_id ... or get_template --template_id ... for specific lookups.

Trust statement

This skill is unofficial and reverse-engineered. It is not affiliated with, endorsed by, or supported by Strong Fitness Ltd. The API surface may change without notice. Use at your own risk. The author assumes no liability for data loss or account restrictions resulting from use of this skill.

More in Data & APIs