Moxe Health · Authentication Profile

Moxe Health Authentication

Authentication

Moxe Health secures its APIs with oauth2 and apiKey across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

HealthcareUnited StatesInteroperabilityClinical DataPayerProviderEHRHealth Data ExchangeClaimsRisk Adjustment
Methods: oauth2, apiKey Schemes: 2 OAuth flows: clientCredentials API key in: header

Security Schemes

moxe_auth oauth2
· flows: clientCredentials
x-api-key apiKey
· in: header ()

Source

Authentication Profile

Raw ↑
generated: '2026-07-24'
method: searched
source: openapi/moxe-health-chart-retrieval-initiate-openapi.json, openapi/moxe-health-chart-retrieval-status-openapi.json,
  openapi/moxe-health-claim-management-initiate-openapi.json, openapi/moxe-health-claim-management-status-openapi.json
docs: https://developer.moxehealth.com/docs/authentication
summary:
  types:
  - oauth2
  - apiKey
  oauth2_flows:
  - clientCredentials
  api_key_in:
  - header
notes: >-
  Every request must present TWO credentials issued by Moxe during partner onboarding:
  (1) an OAuth2 client-credentials bearer access token, and (2) a static API key. The
  bearer token is obtained from a Moxe-provided token endpoint by POSTing grant_type=client_credentials
  with client_id, client_secret, and an audience value (all provided by Moxe). The token
  response returns access_token, token_type=Bearer, and expires_in=900 (15 minutes). The
  token is then sent on API calls in a NON-STANDARD header named "Authentication: Bearer
  {access_token}" (not the conventional "Authorization" header), alongside "x-api-key:
  {api_key}". The OpenAPI additionally declares a custom API Gateway request authorizer
  ("${environment}-chart-retrieval-api-authorizer"). Credentials are not self-serve; they
  are granted only under a partner onboarding agreement.
schemes:
- name: moxe_auth
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://${environment}-api.moxehealth.com/oauth/token
    scopes: 2
    token_ttl_seconds: 900
    audience_required: true
  sources:
  - openapi/moxe-health-chart-retrieval-initiate-openapi.json
  - openapi/moxe-health-chart-retrieval-status-openapi.json
  - openapi/moxe-health-claim-management-initiate-openapi.json
  - openapi/moxe-health-claim-management-status-openapi.json
- name: x-api-key
  type: apiKey
  in: header
  parameter_name: x-api-key
  sources:
  - openapi/moxe-health-chart-retrieval-initiate-openapi.json
  - openapi/moxe-health-chart-retrieval-status-openapi.json
  - openapi/moxe-health-claim-management-initiate-openapi.json
  - openapi/moxe-health-claim-management-status-openapi.json

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/moxe-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 email required.

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