Sensely · OAuth Scopes

Sensely OAuth Scopes

OAuth 2.0 probed

Sensely uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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.

CompanyHealthcareDigital HealthConversational AIVirtual AssistantSymptom CheckerPatient EngagementHealth InsuranceMental HealthSDK

Scopes: 0 Flows: Method: probed

Scopes (0)

Sensely implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Sensely publishes no scopes or permissions reference. The only authorization vocabulary that can be read without credentials is the scope list advertised by its Cognito user pool, which is the stock OIDC set — Cognito supports custom resource-server scopes and none are declared here. The partner credential flow at apis.sensely.com/authenticate/authenticate is not scope-bearing: it returns an opaque token pair, and any per-partner entitlement is carried by the procedureId and program code rather than by a scope.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-26'
method: probed
source: >-
  https://cognito-idp.us-west-1.amazonaws.com/us-west-1_pMO3JfnoS/.well-known/openid-configuration
  (HTTP 200, fetched 2026-08-26) — the discovery document for the Amazon Cognito user pool named in
  Sensely's own published Web SDK bundle.
api: sensely-platform-api
note: >-
  Sensely publishes no scopes or permissions reference. The only authorization vocabulary that can be
  read without credentials is the scope list advertised by its Cognito user pool, which is the stock
  OIDC set — Cognito supports custom resource-server scopes and none are declared here. The partner
  credential flow at apis.sensely.com/authenticate/authenticate is not scope-bearing: it returns an
  opaque token pair, and any per-partner entitlement is carried by the procedureId and program code
  rather than by a scope.
scope_count: 4
scopes:
- name: openid
  description: 'Standard OIDC scope; requests an id token.'
  source: cognito-discovery
- name: email
  description: "Grants access to the user's email address and email_verified claims."
  source: cognito-discovery
- name: phone
  description: "Grants access to the user's phone_number and phone_number_verified claims."
  source: cognito-discovery
- name: profile
  description: 'Grants access to standard OIDC profile claims.'
  source: cognito-discovery
custom_scopes: []
gaps:
- 'No custom resource-server scopes declared on the Cognito pool.'
- 'No published permissions or roles reference for partner API access.'

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/sensely-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.