WeFitter profile API
Profiles are containers for wearables data.The profiles can be seen as an extension of users in a different system.Profiles are anonymous objects which can participate in teams and challenges.Keep in mind, listing profiles and creating profiles need an administrative bearer token, all profile specific actionsneed a seperate bearer token that is returned after creating a profile. This bearer token is used in place of theadministrative bearer token. (see profile create action for more information)
WeFitter profile API is one of 9 APIs that WeFitter publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Profile. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.
This API exposes 34 operations across 29 paths, and defines 33 schemas. It is described by OpenAPI 3.2.0, at version v1.3.
Requests are made against a single base URL, https://api.wefitter.com/api/v1.3.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
WeFitter profile API declares
3 security schemes
for authenticating requests.
It accepts HTTP basic authentication (Basic).
An API key is passed in the header as Authorization (BearerProfile).
An API key is passed in the header as Authorization (BearerAdmin).
By default, every request must be authenticated.
Basic— Basic Authentication is used to create administrator bearer tokens. Once a bearer token has been made, remove this auth. ('logout' in Swagger')BearerProfile— Bearer authentication for logged-in profiles. When using the GUI, please don't forget to prefix your bearer tokens with the text 'bearer', followed by a space.BearerAdmin— Bearer authentication for administrators. When using the GUI, please don't forget to prefix your bearer tokens with the text 'bearer', followed by a space.
Paths & Operations 34
Across 29 paths, the API surfaces 34 operations — 1 DELETE, 29 GET, 1 PATCH, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Profiles are containers for wearables data. The profiles can be seen as an extension of users in a different system. Profiles are anonymous objects which can participate in teams…
Schemas 33
The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are ProfileChallengeList (25 properties), ProfileDetail (22 properties), Workout (13 properties), Activity (13 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from WeFitter 8
Other APIs WeFitter publishes across the network.
This is an independent, third-party profile of WeFitter profile 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.