Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

WeFitter connection API

Connections are the links between profiles and their wearables.

WeFitter connection API is one of 9 APIs that WeFitter publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include connection. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 2 operations across 1 path, and defines 2 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.

2 operations 1 paths 2 schemas 1 DELETE1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
v1.3
Base URL
https://api.wefitter.com/api/v1.3
Authentication
basic, API Key, API Key
License
BSD License
Terms of Service
Resource Areas
1

Authentication & Security 3

WeFitter connection 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 2

Across 1 path, the API surfaces 2 operations — 1 DELETE, 1 POST. Each is listed below with its method, path, parameters, and response codes.

connection 2

Connections are the links between profiles and their wearables.

POST
/connection/{connection_slug}/connect/
Connect wearable
connection_connect_create 2 params → 200
DELETE
/connection/{connection_slug}/connect/
Disconnect Wearable
connection_connect_delete 2 params → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are ProfileAsProfilePublicId (2 properties), AppConnectionUrl (1 property). Each schema is shown below with its type and property counts.

ProfileAsProfilePublicId
object
2 properties 1 required
AppConnectionUrl
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wefitter-connection-api-openapi.yml Raw ↑

Other APIs WeFitter publishes across the network.

WeFitter app API
WeFitter challenge API
WeFitter insights API
WeFitter loyalty API
WeFitter notification API
WeFitter profile API
WeFitter team API
WeFitter token API