Neko Health · Authentication Profile

Neko Health Authentication

Authentication

Neko Health secures its APIs with oauth2 and openIdConnect across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, clientCredentials, implicit, deviceCode, and ciba flow(s).

CompanyHealthHealthcarePreventive HealthMedicalBody ScanDiagnosticsConsumer HealthOpenID ConnectSweden
Methods: oauth2, openIdConnect Schemes: 1 OAuth flows: authorizationCode, clientCredentials, implicit, deviceCode, ciba API key in:

Security Schemes

NekoOIDC openIdConnect

Source

Authentication Profile

neko-health-authentication.yml Raw ↑ 
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: >-
  Derived from the live Duende IdentityServer OIDC discovery document at
  account.nekohealth.com. This is the identity provider for the Neko patient
  application (client_id patientui); Neko publishes no third-party developer API.
  No OpenAPI is available in the repo, so this profile is captured from the
  discovery metadata rather than from securitySchemes.
summary:
  types:
  - oauth2
  - openIdConnect
  oauth2_flows:
  - authorizationCode
  - clientCredentials
  - implicit
  - deviceCode
  - ciba
  pkce: true
  login_methods:
  - phone
  - bankid
schemes:
- name: NekoOIDC
  type: openIdConnect
  openIdConnectUrl: https://account.nekohealth.com/.well-known/openid-configuration
  issuer: https://account.nekohealth.com
  authorization_endpoint: https://account.nekohealth.com/connect/authorize
  token_endpoint: https://account.nekohealth.com/connect/token
  userinfo_endpoint: https://account.nekohealth.com/connect/userinfo
  end_session_endpoint: https://account.nekohealth.com/connect/endsession
  revocation_endpoint: https://account.nekohealth.com/connect/revocation
  introspection_endpoint: https://account.nekohealth.com/connect/introspect
  device_authorization_endpoint: https://account.nekohealth.com/connect/deviceauthorization
  pushed_authorization_request_endpoint: https://account.nekohealth.com/connect/par
  id_token_signing_alg: RS256
  token_endpoint_auth_methods:
  - client_secret_basic
  - client_secret_post
  scopes:
  - openid
  - profile
  - api.backend
  - offline_access

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact 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 security artifact 
curl "https://apis.io/api/v1/security/neko-health-authentication"
All security posture 
curl "https://apis.io/api/v1/security?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.