Headspace
Headspace is a global mental health platform offering consumer mindfulness, meditation, and sleep content alongside Headspace Care (formerly Ginger) — on-demand coaching, therapy, and psychiatry — and Headspace EAP. The B2B business (Headspace for Organizations) serves 4,000+ employers, health plans, and consultants in 190+ countries with a stratified care model (AI companion Ebb, coaches, therapists, psychiatrists). Integration surfaces for enterprise customers — eligibility file feeds, SSO, SCIM, benefit-platform connectors — are delivered under enterprise contracts and are not exposed via a public developer portal. There is no public REST API, no published OpenAPI specification, and no self-serve partner onboarding.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Headspace the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Headspace scores 16.0/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Headspace
Each block below is one kind of artifact we hold for Headspace. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Headspace — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 8
The organization behind the API
Scroll within the panel for all 8 ·
Other 11
Properties that don't map to a standard resource type
Scroll within the panel for all 11 ·
← All providers · Data indexed from github.com/api-evangelist/headspace · machine-readable index on apis.io