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 2.0, at version v1.3.
Requests are made against the 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 defines a basic scheme (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), Activity (13 properties), Workout (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.