Color · Authentication Profile
Color Authentication
Authentication
Color secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.
CompanyHealthHealthcareGenomicsOncologyCancer CarePreventive HealthEligibilityVirtual CareDiagnosticsLaboratoryEmployee Benefits
Methods: apiKey
Schemes: 1
OAuth flows:
API key in: header
Security Schemes
Bearer apiKey
· in: header ()
Source
Authentication Profile
generated: '2026-08-15'
method: searched
source: https://docs.color.com/reference
docs: https://docs.color.com/docs/getting-started-with-color-apis
summary:
types:
- apiKey
api_key_in:
- header
oauth2_flows: []
notes: >-
API access uses a per-environment static bearer token issued by Color and sent
as "Authorization: Bearer <token>". Staging and production each have their own
token and base host, and tokens are handed out by a Color representative during
partner onboarding — there is no self-service key issuance. Portal/user sign-in
is separate and handled via SAML 2.0 SSO.
schemes:
- name: Bearer
type: apiKey
in: header
header_name: Authorization
value_format: Bearer <token>
applied: root-level security requirement, so every one of the 13 operations requires
it
description: >-
Per-environment API token in the Authorization header. Obtain separate staging
and production tokens from Color.
sources:
- openapi/_original/color-external-api-v1-openapi.json
note: >-
Color declares this as an apiKey-in-header scheme rather than http/bearer even
though the value carries the "Bearer " prefix. Tooling that keys off
`scheme: bearer` will not recognise it. Verbatim from Color's spec; not
corrected here.
issuance:
self_service: false
process: Requested from a Color representative during partner onboarding.
environments:
production: https://api.color.com/api/v1/external
staging: https://api.staging.color.com/api/v1/external
staging_legacy: https://external.staging.color.com/api/v1
rotation_policy: not published
expiry: not published
failure_semantics:
status: 403
body: Authentication token was not provided or accepted.
note: >-
Color returns 403, not 401, and sends no WWW-Authenticate challenge. An agent
branching on 401 will never see an auth failure from this API.
scopes:
supported: false
note: >-
No OAuth and no scope surface. Authorisation is implicit in the token — a token
is bound to an organisation and its populations. scopes/ is deliberately not
emitted.
sso:
protocol: SAML 2.0
idp_initiated: false
acs_url: https://colorhealth.kinde.com/login/saml/callback
sp_initiated_bookmark: https://home.color.com/start-sso?domain=<email_domain>
identity_platform: Kinde
docs: https://docs.color.com/docs/sso-integration
note: Portal sign-in only; not usable for API authentication.
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
This security artifact
curl "https://apis.io/api/v1/security/color-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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.