Fitbit | Operate As Docs

Connect your client's Fitbit with a sign-in, and call its API through Operate As.

Website: fitbit.com
Connects by: Signing in with Fitbit
Category: Health and fitness
Services: 1
Tools: Pass-through only

Service	Key	Base URL
Fitbit	`fitbit`	`https://api.fitbit.com`

Connecting

Your client presses Connect on their link and approves on Fitbit's own screen. Operate As never sees their password.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "fitbit"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "fitbit"    ]  }]

Permissions

What the client reads	Permission it asks for
See your Fitbit profile	`profile`
See your steps, exercise and active minutes	`activity`
See your heart rate	`heartrate`
See your sleep	`sleep`
See your weight and body fat	`weight`
See and log your food and water	`nutrition`

Pass-through

Fitbit has no ready-made tools yet. Call any endpoint of its API through Operate As instead, with the client's access attached.

Add the client

In Clients, add your client and select Fitbit. Then send them their link.

Your client connects

They sign in with Fitbit and approve.

Find the endpoint

Pick the call from Fitbit's own API docs. Your path is everything after https://api.fitbit.com.

Send it through Operate As

Use the client's ID, the service key fitbit and that path. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../fitbit/1/user/-/profile.json" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../fitbit/1/user/-/profile.json" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If Fitbit refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "detail": "Miller Dental's Fitbit access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Fitbit access ended. Send them their link to reconnect."}

Your webhook receives

{
  "id": "evt_3f9a1c…",
  "type": "connection.expired",
  "createdAt": "2026-10-16T08:00:00+00:00",
  "data": {
    "clientId": "6f1c2a7e-...",
    "clientName": "Miller Dental",
    "provider": "fitbit",
    "services": [
      "fitbit"
    ],
    "reconnectUrl": "https://…"
  }
}

{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "fitbit",    "services": [      "fitbit"    ],    "reconnectUrl": "https://…"  }}