Cambio Healthcare Systems · Authentication Profile

Cambio Healthcare Systems Authentication

Authentication

Cambio Healthcare Systems secures its APIs with apiKey, oauth2, and openIdConnect across 4 declared security schemes, as derived from its OpenAPI definitions.

HealthcareElectronic Health RecordsEHRClinical Decision SupportFHIRHL7InteroperabilityHealth ITSwedenNordicsPatient DataMedical RecordsopenEHRSMART on FHIRCompany
Methods: apiKey, oauth2, openIdConnect Schemes: 4 OAuth flows: API key in: header, query

Security Schemes

apiKeyHeader apiKey
· in: header (Ocp-Apim-Subscription-Key)
apiKeyQuery apiKey
· in: query (subscription-key)
oauth2 oauth2
· flows: ,
openIdConnect openIdConnect

Source

Authentication Profile

Raw ↑
generated: '2026-09-02'
method: searched
source: https://developer.openservices.cambio.se/getting-started
docs: https://developer.openservices.cambio.se/getting-started
note: 'Cambio Open Services requires TWO credentials on every call: an Azure API Management subscription key (the
  "API key" shown in the COS portal profile, sent as Ocp-Apim-Subscription-Key or the subscription-key query parameter)
  AND an OAuth 2.0 bearer access token issued by the Cambio Keycloak realm at https://api.openservices.cambio.se/auth/realms/COS.
  The OpenAPI documents exported by the portal only declare the APIM subscription key; the OAuth layer is documented
  on the Getting started page and in the OpenID Connect discovery document captured under well-known/.'
summary:
  types:
  - apiKey
  - oauth2
  - openIdConnect
  api_key_in:
  - header
  - query
  oauth_grant_types:
  - authorization_code
  - client_credentials
  token_endpoint_auth_methods:
  - private_key_jwt
  - client_secret_basic
  - client_secret_post
  - tls_client_auth
  - client_secret_jwt
  pkce:
  - plain
  - S256
  mtls_supported: true
schemes:
- name: apiKeyHeader
  type: apiKey
  in: header
  parameter: Ocp-Apim-Subscription-Key
  description: Azure API Management subscription key, issued per COS product subscription and shown in the developer-portal
    profile as Primary/Secondary Key.
  source: openapi/ (all 19 exported specs)
- name: apiKeyQuery
  type: apiKey
  in: query
  parameter: subscription-key
  description: Same APIM subscription key passed as a query parameter instead of a header.
  source: openapi/ (all 19 exported specs)
- name: oauth2
  type: oauth2
  flows:
  - authorizationCode
  - clientCredentials
  authorization_endpoint: https://api.openservices.cambio.se/auth/realms/COS/protocol/openid-connect/auth
  token_endpoint: https://api.openservices.cambio.se/auth/realms/COS/protocol/openid-connect/token
  jwks_uri: https://api.openservices.cambio.se/auth/realms/COS/protocol/openid-connect/certs
  introspection_endpoint: https://api.openservices.cambio.se/auth/realms/COS/protocol/openid-connect/token/introspect
  revocation_endpoint: https://api.openservices.cambio.se/auth/realms/COS/protocol/openid-connect/revoke
  description: Cambio Open Services authorization server (Keycloak realm COS). Client-id and client secret are emailed
    after a product subscription is approved. Access is scoped with SMART-on-FHIR style scopes.
  source: https://api.openservices.cambio.se/auth/realms/COS/.well-known/openid-configuration
- name: openIdConnect
  type: openIdConnect
  openIdConnectUrl: https://api.openservices.cambio.se/auth/realms/COS/.well-known/openid-configuration
  issuer: https://api.openservices.cambio.se/auth/realms/COS
  source: probed 2026-09-02, HTTP 200
onboarding:
  signup: https://developer.openservices.cambio.se/signup
  steps:
  - Sign up at the COS developer portal
  - Subscribe to the "Cambio Open Services" product (approval required)
  - Receive client-id and client secret by email
  - Read the API key (Primary/Secondary) from the portal profile
  - Request an access token from the Keycloak token endpoint, then call the API with both the token and the subscription
    key
  approval_required: 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/cambio-healthcare-systems-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.