Cloudhealth Authentication
CloudHealth secures its APIs with http, apiKey, and oauth2 across 4 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, clientCredentials, and refreshToken flow(s).
Security Schemes
Source
Authentication Profile
generated: '2026-09-16'
method: searched
source: https://apidocs.cloudhealthtech.com/#documentation_getting-your-api-key
docs:
- https://apidocs.cloudhealthtech.com/#documentation_how-to-use-the-cloudhealth-api
- https://apidocs.cloudhealthtech.com/#documentation_getting-your-api-key
- https://help.cloudhealthtech.com/graphql-api/#authentication
- https://apps.cloudhealthtech.com/.well-known/oauth-authorization-server
note: Upgraded from the spec-derived profile (openapi/ files are API Evangelist-authored from the docs, see
openapi/_ae-authored/README.md). The REST, GraphQL and MCP surfaces authenticate three different ways.
summary:
types:
- http
- apiKey
- oauth2
api_key_in:
- header
- query
oauth2_flows:
- authorizationCode
- clientCredentials
- refreshToken
schemes:
- name: bearerAuth
surface: REST API (https://chapi.cloudhealthtech.com)
type: http
scheme: bearer
description: >-
Per-user API key (a GUID generated under My Profile > API Key) sent as
"Authorization: Bearer <api_key>". Every request must also send Accept: application/json
(or Content-Type: application/json). Generating a new key invalidates the previous one; the
docs recommend periodic rotation. The API enforces the same organization scoping and role
restrictions as the CloudHealth UI.
evidence: https://apidocs.cloudhealthtech.com/#documentation_how-to-use-the-cloudhealth-api
sources:
- openapi/cloudhealth-aws-accounts-api-openapi.yml
- openapi/cloudhealth-perspectives-api-openapi.yml
- openapi/cloudhealth-reports-api-openapi.yml
- openapi/cloudhealth-search-api-openapi.yml
- openapi/cloudhealth-sso-api-openapi.yml
- name: apiKeyQuery
surface: REST API (https://chapi.cloudhealthtech.com)
type: apiKey
in: query
parameter: api_key
description: The same API key may instead be passed as the api_key query parameter.
evidence: https://apidocs.cloudhealthtech.com/#documentation_how-to-use-the-cloudhealth-api
- name: graphqlAccessToken
surface: GraphQL API (https://apps.cloudhealthtech.com/graphql)
type: http
scheme: bearer
description: >-
Exchange the API key for a token pair with the loginAPI(apiKey) mutation (no auth required),
then send "Authorization: Bearer <accessToken>". Access tokens are valid for 15 minutes; the
refresh token (refresh(token) mutation) is valid for 9 hours. loginCspService / loginCspUser
exchange VMware Cloud Services Platform tokens. FlexOrg sub-organizations require their own
token.
token_lifetimes:
access_token: 15 minutes
refresh_token: 9 hours
token_exchange_operations: [loginAPI, login, refresh, loginCspService, loginCspUser]
evidence:
- https://help.cloudhealthtech.com/graphql-api/#authentication
- graphql/cloudhealth-graphql-public-schema.graphql
- name: mcpOAuth
surface: MCP server (https://apps.cloudhealthtech.com/mcp)
type: oauth2
description: >-
The MCP endpoint answers unauthenticated requests with 401 and
WWW-Authenticate: Bearer resource_metadata="https://apps.cloudhealthtech.com/.well-known/oauth-protected-resource"
(RFC 9728). The authorization server publishes RFC 8414 metadata with PKCE (S256), dynamic
client registration and client ID metadata documents.
issuer: https://apps.cloudhealthtech.com
authorizationUrl: https://apps.cloudhealthtech.com/oauth2/authorize
tokenUrl: https://apps.cloudhealthtech.com/oauth2/token
revocationUrl: https://apps.cloudhealthtech.com/oauth2/revoke
registrationUrl: https://apps.cloudhealthtech.com/oauth2/register
jwks_uri: https://apps.cloudhealthtech.com/oauth2/jwks
flows: [authorizationCode, clientCredentials, refreshToken]
pkce: [S256]
token_endpoint_auth_methods: [client_secret_basic, client_secret_post, none]
scope_count: 4
scopes_ref: scopes/cloudhealth-scopes.yml
evidence:
- well-known/cloudhealth-oauth-authorization-server.json
- well-known/cloudhealth-oauth-protected-resource.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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/security/cloudhealth-authentication"
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.
A second provider on the same verified email joins the account you already have.