Metriport · Arazzo Workflow

Metriport Wearables Connect

Version 1.0.0

Create a devices user, mint a Connect Widget session token, then pull the user's activity and biometrics data from connected wearables.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub HealthcareMedical RecordsFHIRHealth DataWearablesOpen-SourceArazzoWorkflows

Provider

metriport

Workflows

wearables-connect
Create a devices user, mint a connect token, then pull activity and biometrics data.
Implements the Metriport devices sequence end to end: devices user creation, Connect Widget token generation, and activity and biometrics retrieval.
4 steps inputs: appUserId outputs: activity, biometrics, connectToken, userId
1
createUser
Create a Metriport devices user mapped to the application user identifier.
2
getToken
Generate a Connect Widget session token so the user can link wearable providers.
3
getActivity
Retrieve the aggregated activity data across the user's connected wearables.
4
getBiometrics
Retrieve the aggregated biometrics data across the user's connected wearables.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Metriport Wearables Connect
  summary: Create a devices user, mint a Connect Widget session token, then pull the user's activity and biometrics data from connected wearables.
  description: >-
    The canonical Metriport devices flow for wearable and consumer health data. A
    devices user is created from an application user id, a Connect Widget session
    token is generated so the user can link providers, and the aggregated activity
    and biometrics datasets are retrieved across the connected wearables. Every
    step inlines its request so the flow is self-contained.
  version: 1.0.0
sourceDescriptions:
- name: devicesDataApi
  url: ../openapi/metriport-devices-data-api-openapi.yml
  type: openapi
- name: userApi
  url: ../openapi/metriport-user-api-openapi.yml
  type: openapi
workflows:
- workflowId: wearables-connect
  summary: Create a devices user, mint a connect token, then pull activity and biometrics data.
  description: >-
    Implements the Metriport devices sequence end to end: devices user creation,
    Connect Widget token generation, and activity and biometrics retrieval.
  inputs:
    type: object
    required:
    - appUserId
    properties:
      appUserId:
        type: string
        description: Application-side user identifier mapped to a Metriport devices user.
  steps:
  - stepId: createUser
    description: Create a Metriport devices user mapped to the application user identifier.
    operationId: createDevicesUser
    parameters:
    - name: appUserId
      in: query
      value: $inputs.appUserId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      userId: $response.body#/userId
  - stepId: getToken
    description: Generate a Connect Widget session token so the user can link wearable providers.
    operationId: getConnectToken
    parameters:
    - name: userId
      in: query
      value: $steps.createUser.outputs.userId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      connectToken: $response.body#/token
  - stepId: getActivity
    description: Retrieve the aggregated activity data across the user's connected wearables.
    operationId: getActivity
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      activity: $response.body
  - stepId: getBiometrics
    description: Retrieve the aggregated biometrics data across the user's connected wearables.
    operationId: getBiometrics
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      biometrics: $response.body
  outputs:
    userId: $steps.createUser.outputs.userId
    connectToken: $steps.getToken.outputs.connectToken
    activity: $steps.getActivity.outputs.activity
    biometrics: $steps.getBiometrics.outputs.biometrics

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/metriport-wearables-connect-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.