Withings Oauth2 API
The Withings API uses OAuth 2.0, an industry-standard protocol for authorization. OAuth 2.0 enables your application to access user-specific data with a secure and seamless way without requiring users to share their Withings credentials with your app. The Withings API supports the Authorization Code Flow, which is suitable for server-sideapplications. In this flow, your application will obtain an authorization code from the user, which can then be exchanged for an access token and refresh token. There are two ways to obtain the authorization code: 1. **Web Authorization Flow**: Redirect the user to the Withings authorization endpoint,where they can grant permission for your app to access their Withings data. 2. **Account Creation Flow (contract partners only)**: Obtain the authorizationcode after account creation (Cellular Devices/SDK only) . To use OAuth 2.0 with the Withings API, follow these general steps: 1. **Request user authorization/Create an account**: Use one of the two methodsmentioned above to obtain an authorization code from the user. 2. **Obtain an access token**: Exchange the authorization code for an access tokenand refresh token. 3. **Access the API**: Include the access token in your API requests to access user-specificdata from the Withings API. 4. **Refresh tokens**: Use the refresh token to obtain new access tokens when thecurrent ones expire. Please refer to the appropriate [Integration Guide](https://developer.withings.com/developer-guide/v3/withings-solutions/integration-guides)to know which method you should use.
Withings Oauth2 API is one of 18 APIs that Withings publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 8 JSON Schema definitions.
Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and 8 JSON Schemas.
This API exposes 7 operations across 7 paths. It is described by OpenAPI 3.2.0, at version 2.0.
Requests are made against a single base URL, https://wbsapi.withings.net/.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 7
Across 7 paths, the API surfaces 7 operations — 1 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.
The Withings API uses OAuth 2.0, an industry-standard protocol for authorization.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Withings 12
Other APIs Withings publishes across the network.
This is an independent, third-party profile of Withings Oauth2 API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.