Arbital Health · Authentication Profile

Arbital Health Authentication

Authentication

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

CompanyHealthcareHealth InsuranceValue-Based CareActuarialClaimsPayersProvidersAnalyticsArtificial Intelligence
Methods: openIdConnect, oauth2 Schemes: 1 OAuth flows: authorizationCode API key in:

Security Schemes

propelauth-oidc openIdConnect

Source

Authentication Profile

arbital-health-authentication.yml Raw ↑
generated: '2026-08-06'
method: probed
source: https://auth.arbitalhealth.com/.well-known/openid-configuration
docs: null
summary:
  types:
  - openIdConnect
  - oauth2
  api_key_in: []
  oauth2_flows:
  - authorizationCode
  note: >-
    Derived from the live OpenID Connect discovery document, not from an OpenAPI —
    Arbital Health publishes no machine-readable API contract. The platform API at
    platform.arbitalhealth.com/api returns 401 {"error":"Unauthorized"} to every
    anonymous request, so the credential material it accepts (bearer JWT vs session
    cookie) could not be confirmed without a customer account.
schemes:
- name: propelauth-oidc
  type: openIdConnect
  openIdConnectUrl: https://auth.arbitalhealth.com/.well-known/openid-configuration
  issuer: https://auth.arbitalhealth.com
  provider: PropelAuth
  sources:
  - well-known/arbital-health-openid-configuration.json
  endpoints:
    authorization: https://auth.arbitalhealth.com/propelauth/oauth/authorize
    token: https://auth.arbitalhealth.com/propelauth/oauth/token
    userinfo: https://auth.arbitalhealth.com/propelauth/oauth/userinfo
    jwks: https://auth.arbitalhealth.com/.well-known/jwks.json
  grant_types_supported:
  - authorization_code
  response_types_supported:
  - code
  code_challenge_methods_supported:
  - S256
  token_endpoint_auth_methods_supported:
  - client_secret_basic
  - client_secret_post
  id_token_signing_alg_values_supported:
  - RS256
  subject_types_supported:
  - public
  scopes_supported:
  - openid
  - email
  - profile
  claims_supported:
  - email
  - email_verified
  - exp
  - first_name
  - last_name
  - iat
  - iss
  - picture_url
observations:
- Authorization Code + PKCE (S256) is the only advertised flow; no client_credentials,
  no device flow, no refresh_token grant advertised.
- No /.well-known/oauth-authorization-server (RFC 8414) and no
  /.well-known/oauth-protected-resource (RFC 9728) are published — both 404.
- Single-tenant SaaS login. There is no public developer registration path; OAuth
  clients are provisioned by Arbital Health for its customers.
x-evidence:
  fetched: '2026-08-06'
  probes:
  - url: https://auth.arbitalhealth.com/.well-known/openid-configuration
    status: 200
  - url: https://auth.arbitalhealth.com/.well-known/jwks.json
    status: 200
  - url: https://platform.arbitalhealth.com/api/v1
    status: 401