Headway
Headway is a New York-based mental health technology company building the largest insurance-credentialed network of therapists, psychiatrists, and prescribers in the United States. Founded in 2019 by Andrew Adams, Jake Sussman, Dan Ross, and Kevin Chan, Headway operates a two-sided platform that helps independent mental health providers get credentialed with major commercial payers, Medicare Advantage, and select Medicaid managed care plans, while helping patients find affordable in-network therapy. The platform handles insurance credentialing (claimed to be as fast as 30 days with top payers), benefit verification, claims submission and adjudication, appeals, clawback protection, biweekly guaranteed provider payments, scheduling, telehealth, EHR-style clinical notes, and compliance tooling. Headway is free to join for providers and earns revenue through commissions paid by insurance carriers. Its payer network spans 100+ plans across all 50 states and DC, including Aetna, Anthem Blue Cross Blue Shield, Cigna, UnitedHealthcare, Optum, Oscar, Oxford, Evernorth, and Blue Cross Blue Shield of Massachusetts, supporting more than 70,000 licensed providers delivering care in 57+ languages across 20+ clinical specialties. Headway has raised over $325M from Andreessen Horowitz, Thrive, Accel, GV, Spark Capital, Forerunner Ventures, and Health Care Service Corporation, with a valuation around $2.3B. Headway does not publish a public developer API, OpenAPI specification, SDK, or partner integration program — its platform is offered exclusively as a managed SaaS to providers, group practices, and health plans. The headway.co GitHub organization exists but only contains forks of third-party open-source libraries (Starlette, Pydantic, Flower, etc.) used internally by Headway's engineering teams. Note that the unrelated headwayapp.co company (a product changelog widget) does publish a public REST API and should not be confused with this provider.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Headway the way a machine reads it — 2 machine-readable artifacts, 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 — Headway scores 11.0/100 (minimal), 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Headway
Each block below is one kind of artifact we hold for Headway. 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 2
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 Headway — 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.
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/headway-co · machine-readable index on apis.io