Neko Health · OAuth Scopes

Neko Health OAuth Scopes

OAuth 2.0 searched

Neko Health publishes 4 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Neko Health API on a user’s behalf.

Tokens are issued from https://account.nekohealth.com/connect/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.

CompanyHealthHealthcarePreventive HealthMedicalBody ScanDiagnosticsConsumer HealthOpenID ConnectSweden

Scopes: 4 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://account.nekohealth.com/connect/authorize

Token URL
https://account.nekohealth.com/connect/token

Flows
authorizationCode

Scopes (4)

Scope	Description	Flows
openid	Standard OpenID Connect scope; requests an ID token for the subject.	authorizationCode
profile	Access to the end-user's basic profile claims.	authorizationCode
api.backend	Access to Neko's backend resource API used by the patient application.	authorizationCode
offline_access	Requests a refresh token for long-lived offline access.	authorizationCode

📄 Provider scope reference: https://account.nekohealth.com/.well-known/oauth-authorization-server

Source

OAuth Scopes

generated: '2026-07-20'
method: searched
source: https://account.nekohealth.com/.well-known/openid-configuration
docs: https://account.nekohealth.com/.well-known/oauth-authorization-server
note: >-
  Scopes advertised by the Neko patient-app OIDC provider (Duende IdentityServer).
  These are consumer/patient authentication scopes, not a third-party API
  permission surface. Descriptions are standard OIDC meanings; api.backend is
  Neko's own backend resource scope.
schemes:
- name: NekoOIDC
  source: https://account.nekohealth.com/.well-known/openid-configuration
  flows:
  - flow: authorizationCode
    authorizationUrl: https://account.nekohealth.com/connect/authorize
    tokenUrl: https://account.nekohealth.com/connect/token
scopes:
- scope: openid
  description: Standard OpenID Connect scope; requests an ID token for the subject.
  flows: [authorizationCode]
- scope: profile
  description: Access to the end-user's basic profile claims.
  flows: [authorizationCode]
- scope: api.backend
  description: Access to Neko's backend resource API used by the patient application.
  flows: [authorizationCode]
- scope: offline_access
  description: Requests a refresh token for long-lived offline access.
  flows: [authorizationCode]

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/neko-health-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.