Kyo · OAuth Scopes

Kyo OAuth Scopes

OAuth 2.0 searched

Kyo publishes 2 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 Kyo API on a user’s behalf.

Tokens are issued from https://api.attain.kyocare.com/oauth/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.

CompanyHealthcareAutismABA TherapyBehavioral HealthPatient EngagementDigital HealthSchedulingPrivate API

Scopes: 2 Flows: authorizationCode, clientCredentials Method: searched

OAuth endpoints

Authorization URL
https://api.attain.kyocare.com/oauth/authorize

Token URL
https://api.attain.kyocare.com/oauth/token

Flows
authorizationCodeclientCredentials

Scopes (2)

Scope	Description	Flows
openid	Standard OpenID Connect scope; requests an ID token asserting the end user's identity.	authorizationCode
email	Releases the end user's email address and email_verified claim to the client.	authorizationCode

📄 Provider scope reference: https://api.attain.kyocare.com/.well-known/oauth-authorization-server

Source

OAuth Scopes

generated: '2026-07-19'
method: searched
source: https://api.attain.kyocare.com/.well-known/openid-configuration
docs: https://api.attain.kyocare.com/.well-known/oauth-authorization-server
note: Scopes read verbatim from the published `scopes_supported` of the Attain platform
  API discovery document. Kyo publishes no scope/permission reference page, so this is
  the complete advertised scope surface — standard OIDC identity scopes only, with no
  resource-level scopes exposed publicly.
schemes:
- name: oauth2
  source: well-known/kyocare-openid-configuration.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.attain.kyocare.com/oauth/authorize
    tokenUrl: https://api.attain.kyocare.com/oauth/token
  - flow: clientCredentials
    tokenUrl: https://api.attain.kyocare.com/oauth/token
scopes:
- scope: openid
  description: Standard OpenID Connect scope; requests an ID token asserting the end
    user's identity.
  flows:
  - authorizationCode
  sources:
  - well-known/kyocare-openid-configuration.json
- scope: email
  description: Releases the end user's email address and email_verified claim to the
    client.
  flows:
  - authorizationCode
  sources:
  - well-known/kyocare-openid-configuration.json

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/kyocare-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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