How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

b.well Users API

The Users API from b.well — 2 operation(s) for users.

b.well Users API is one of 5 APIs that b.well publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 2 operations across 2 paths. It is described by OpenAPI 3.2.0, at version 1.0.11.

Requests are made against 2 base URLs: https://user-data-ops.client-sandbox.icanbwell.com, https://user-data-ops.prod.icanbwell.com.

2 operations 2 paths 0 schemas 1 DELETE1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.11
Base URL
https://api.client-sandbox.icanbwell.com/v1
Authentication
API Key, API Key, API Key, API Key, API Key, API Key
License
Terms of Service
Resource Areas
1

Authentication & Security 6

b.well Users API declares 6 security schemes for authenticating requests. An API key is passed in the header as Authorization (HMACAuth). An API key is passed in the header as x-bwell-content-sha512 (HMACContentSHA512). An API key is passed in the header as Host (HMACHost). An API key is passed in the header as x-bwell-date (HMACDate). An API key is passed in the header as x-bwell-client-user-token (HMACClientUserToken). An API key is passed in the header as x-bwell-client-key (HMACClientKey).

  • HMACAuth — HMAC Authentication Authorization using a secret key and signature content. To use HMAC authentication, clients need to generate an HMAC signature using their…
  • HMACContentSHA512 — The Base64 encoded SHA512 hash of request content.
  • HMACHost — The DNS Host associated with the request.
  • HMACDate — UTC Timestamp in RFC1123 format.
  • HMACClientUserToken — Client specific user authentication token.
  • HMACClientKey — Client key. Provided to the client by bwell.

Paths & Operations 2

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

Users 2
POST
/users/{id}/data-exports
Initiate user data export
1 param → 202401404500
DELETE
/users/{id}
Initiate user data deletion
1 param → 202401404500

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

b-well-users-api-openapi.yml Raw ↑

Other APIs b.well publishes across the network.

b.well Application APIs
b.well FHIR Server
b.well Health SDK for AI (MCP Server)
b.well Webhook API
Where this information came from

This is an independent, third-party profile of b.well Users 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.