Cloudhealth Technologies Authentication

generated: '2026-07-18'
method: searched
source: https://apidocs.cloudhealthtech.com/
docs: https://apidocs.cloudhealthtech.com/
description: >-
  The CloudHealth Platform REST API authenticates every request with a per-user
  API Key — a globally unique identifier (GUID) that CloudHealth generates for
  each user from their profile settings in the platform. There is no OAuth flow;
  the same key is presented on every call and the API enforces the same
  authentication and role/authorization checks as the CloudHealth Platform UI, so
  a key only sees data scoped to that user's organization and role. The key may be
  supplied either as an HTTP bearer token or as an api_key query parameter.
summary:
  types: [apiKey, http]
  api_key_in: [header, query]
  oauth2_flows: []
schemes:
  - name: BearerApiKey
    type: http
    scheme: bearer
    description: >-
      Preferred method. Send the API Key as a bearer token in the Authorization
      header: `Authorization: Bearer <API_KEY>`.
    sources: [https://apidocs.cloudhealthtech.com/]
  - name: ApiKeyQuery
    type: apiKey
    in: query
    parameter_name: api_key
    description: >-
      Alternative method. Append the API Key as a query parameter:
      `?api_key=<API_KEY>`.
    sources: [https://apidocs.cloudhealthtech.com/]
notes: >-
  For POST/PUT requests a `Content-Type: application/json` header is required or
  the API returns HTTP 422 Unprocessable Entity. Responses are JSON; send
  `Accept: application/json`.