LightForce Orthodontics · Authentication Profile

Lightforce Orthodontics Authentication

Authentication

LightForce Orthodontics secures its APIs with oauth2 and openIdConnect across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, clientCredentials, implicit, deviceCode, and refreshToken flow(s).

CompanyHealthcareOrthodonticsMedical DevicesDental3D PrintingManufacturingIdentity
Methods: oauth2, openIdConnect Schemes: 2 OAuth flows: authorizationCode, clientCredentials, implicit, deviceCode, refreshToken API key in:

Security Schemes

LightForceOIDC openIdConnect
LightForceOAuth2 oauth2
· flows: authorizationCode, clientCredentials, implicit, deviceCode

Source

Authentication Profile

lightforce-orthodontics-authentication.yml Raw ↑ 
generated: '2026-07-19'
method: searched
source: https://id.lightforceortho.com/.well-known/openid-configuration
docs: https://id.lightforceortho.com/.well-known/openid-configuration
summary:
  types:
  - oauth2
  - openIdConnect
  api_key_in: []
  oauth2_flows:
  - authorizationCode
  - clientCredentials
  - implicit
  - deviceCode
  - refreshToken
  note: Derived from the provider's published OIDC discovery document. LightForce ships no
    public OpenAPI, so no operation-level security requirements could be inspected. This
    identity tenant fronts the LightForce Doctor Portal, not a documented public API.
schemes:
- name: LightForceOIDC
  type: openIdConnect
  openIdConnectUrl: https://id.lightforceortho.com/.well-known/openid-configuration
  issuer: https://id.lightforceortho.com/
  provider: Auth0
  sources:
  - well-known/lightforce-orthodontics-openid-configuration.json
- name: LightForceOAuth2
  type: oauth2
  issuer: https://id.lightforceortho.com/
  flows:
  - flow: authorizationCode
    authorizationUrl: https://id.lightforceortho.com/authorize
    tokenUrl: https://id.lightforceortho.com/oauth/token
  - flow: clientCredentials
    tokenUrl: https://id.lightforceortho.com/oauth/token
  - flow: implicit
    authorizationUrl: https://id.lightforceortho.com/authorize
  - flow: deviceCode
    deviceAuthorizationUrl: https://id.lightforceortho.com/oauth/device/code
    tokenUrl: https://id.lightforceortho.com/oauth/token
  sources:
  - well-known/lightforce-orthodontics-openid-configuration.json
endpoints:
  authorization: https://id.lightforceortho.com/authorize
  token: https://id.lightforceortho.com/oauth/token
  userinfo: https://id.lightforceortho.com/userinfo
  jwks: https://id.lightforceortho.com/.well-known/jwks.json
  revocation: https://id.lightforceortho.com/oauth/revoke
  registration: https://id.lightforceortho.com/oidc/register
  device_authorization: https://id.lightforceortho.com/oauth/device/code
  mfa_challenge: https://id.lightforceortho.com/mfa/challenge
capabilities:
  pkce_methods:
  - S256
  - plain
  token_endpoint_auth_methods:
  - client_secret_basic
  - client_secret_post
  - private_key_jwt
  - none
  token_endpoint_auth_signing_algs:
  - RS256
  - RS384
  - PS256
  response_modes:
  - query
  - fragment
  - form_post
  dynamic_client_registration: true
  token_exchange: true
  mfa: true

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/lightforce-orthodontics-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.