python-fitbit (PyPI: fitbit)

Install

The README documents no pip install line; it installs requirement files from a checkout (sudo pip install -r requirements/base.txt). The PyPI distribution is named fitbit, not python-fitbit.

Registry and repository facts

Read from PyPI and the repository by a script, not typed by hand. Where the metadata does not state something, the row says so. Dates are shown as dates, with the gap to our read, rather than as a verdict on whether the project is alive.

Registry

PyPI: fitbit

Latest version

0.3.1, published 2019-05-242,689 days before our 2026-10-03 read

First published

2012-10-15 · 14 versions published

Licence

Apache 2.0PyPI license field

Platforms

not stated in registry metadata

Requires

not stated

Repository

orcasgit/python-fitbit

Last commit, default branch

2019-08-122,609 days before our 2026-10-03 read · read by git on 2026-10-03

GitHub signals

633 stars · 61 open issues and PRs · not archived · last push to any branch 2024-07-23GitHub API, read 2026-10-03

Registry description: “Fitbit API Wrapper.”

What the README warns about

Each item is the project’s own statement, checked on 2026-10-03, quoted where the wording matters.

• Requirements as the README states them: Python 2.7+, python-dateutil and requests-oauthlib.

  Source: README

• Where Google points Fitbit integrations. The Fit migration guide's table lists "Fitbit Web API" with "Google Health API" as the recommended path, and describes the Google Health API as a web-centric platform for Fitbit and Google device data.

  Source: Google's Fit migration guide (last updated 2026-09-10)

The API underneath

A wrapper inherits every rule of the API it calls. These pages cover that layer directly.

• Fitbit API shutdown: what is confirmed →What is and is not verified about the legacy API's turndown.
• Migrate the Fitbit Web API to Google Health →The re-consent and schema work the move involves.
• Fitbit API integration guide →The API this client was written for.
• Fitbit error code 401 →The token errors a legacy client most often hits.

Other Python packages on this list

Python libraries for fitness APIs: every package side by side, and how to choose →

• garminconnect0.3.17 · 2026-09-29Garmin Connect's web services, signed in as the user with their own credentials.
• garth0.8.0 · 2026-03-28Garmin's SSO login and the Garmin Connect API, through the mobile auth approach the README says Garmin's change broke.
• stravalib2.6.0 · 2026-08-27The Strava V3 REST API, through a stravalib.client.Client class, per the README.
• oura-ring1.0.1 · 2026-06-22The Oura API v2.
• oura1.3.0 · 2024-04-23The Oura API, with v2 clients under oura.v2 (OuraClientV2, OuraClientDataFrameV2) whose methods are named after the URL paths, per the README.
• withings-api2.4.0 · 2022-02-08The Withings Health API over OAuth 2.0, through WithingsAuth and WithingsApi, per the README.

Questions

Does python-fitbit work with the Google Health API?

Nothing in its README says so. python-fitbit was written for the legacy Fitbit Web API, its latest PyPI release is from 2019, and Google's Fit migration guide lists the Google Health API as the recommended path for Fitbit Web API integrations — a different API with Google OAuth, which this client does not mention.

What is the pip package name for python-fitbit?

fitbit. The repository is orcasgit/python-fitbit, but the PyPI distribution is named fitbit, and there is no PyPI project called python-fitbit. The README itself documents installing requirement files from a checkout rather than a pip install line.