b.well · OAuth Scopes

b.well OAuth Scopes

OAuth 2.0 searched

b.well publishes 4 OAuth 2.0 scopes via the authorizationCode and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the b.well API on a user’s behalf.

Tokens are issued from https://fhir-bwell.auth.us-east-1.amazoncognito.com/oauth2/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyHealthHealthcareDigital HealthFHIRHealth DataInteroperabilityPatient AccessHealth RecordsMCP

Scopes: 4 Flows: authorizationCode, clientCredentials Method: searched

OAuth endpoints

Authorization URL
https://fhir-bwell.auth.us-east-1.amazoncognito.com/oauth2/authorize https://client-sandbox-fhir.auth.us-east-1.amazoncognito.com/oauth2/authorize

Token URL
https://fhir-bwell.auth.us-east-1.amazoncognito.com/oauth2/token https://client-sandbox-fhir.auth.us-east-1.amazoncognito.com/oauth2/token

Flows
authorizationCodeclientCredentials

Scopes (4)

Scope	Description	Flows
openid	OpenID Connect — issue an ID token identifying the authenticated subject.	authorizationCode
profile	Access to the subject's basic profile claims.	authorizationCode
email	Access to the subject's email address claim.	authorizationCode
phone	Access to the subject's phone number claim.	authorizationCode

📄 Provider scope reference: https://developer.bwell.com/docs/system-auth

Source

OAuth Scopes

generated: '2026-08-06'
method: searched
source: https://fhir.icanbwell.com/.well-known/smart-configuration
docs: https://developer.bwell.com/docs/system-auth
notes: >-
  b.well documents scope-based authorization but does not publish a scope reference
  page. Client IDs are "assigned specific scopes during onboarding based on your
  integration requirements", so the full scope vocabulary is negotiated per customer
  and is not publicly enumerable. The scopes recorded below are the ones actually
  advertised anonymously in the SMART-on-FHIR configuration documents served by the
  production and sandbox FHIR hosts — the identity scopes of the underlying AWS
  Cognito authorization server. No SMART clinical scopes (patient/*.read and the
  like) are advertised there.
schemes:
- name: SMART on FHIR / OAuth 2.0 (production)
  source: https://fhir.icanbwell.com/.well-known/smart-configuration
  file: well-known/b-well-smart-configuration.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://fhir-bwell.auth.us-east-1.amazoncognito.com/oauth2/authorize
    tokenUrl: https://fhir-bwell.auth.us-east-1.amazoncognito.com/oauth2/token
  - flow: clientCredentials
    tokenUrl: https://fhir-bwell.auth.us-east-1.amazoncognito.com/oauth2/token
- name: SMART on FHIR / OAuth 2.0 (client-sandbox)
  source: https://fhir.client-sandbox.icanbwell.com/.well-known/smart-configuration
  file: well-known/b-well-smart-configuration-sandbox.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://client-sandbox-fhir.auth.us-east-1.amazoncognito.com/oauth2/authorize
    tokenUrl: https://client-sandbox-fhir.auth.us-east-1.amazoncognito.com/oauth2/token
scopes:
- scope: openid
  description: OpenID Connect — issue an ID token identifying the authenticated subject.
  flows: [authorizationCode]
  sources: [well-known/b-well-smart-configuration.json, well-known/b-well-smart-configuration-sandbox.json]
- scope: profile
  description: Access to the subject's basic profile claims.
  flows: [authorizationCode]
  sources: [well-known/b-well-smart-configuration.json, well-known/b-well-smart-configuration-sandbox.json]
- scope: email
  description: Access to the subject's email address claim.
  flows: [authorizationCode]
  sources: [well-known/b-well-smart-configuration.json, well-known/b-well-smart-configuration-sandbox.json]
- scope: phone
  description: Access to the subject's phone number claim.
  flows: [authorizationCode]
  sources: [well-known/b-well-smart-configuration.json, well-known/b-well-smart-configuration-sandbox.json]
gaps:
- issue: no published scope reference
  detail: >-
    Neither developer.bwell.com nor the SMART configuration enumerates the data-access
    scopes granted to a client credentials integration. An integrator cannot see, before
    onboarding, which scopes exist or what each one unlocks.
  fixable_by: b.well

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/b-well-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.