Lyra Health Mental Health Benefits REST API

Lyra Health mental health benefits REST API for employers, health plans, and HR platforms to manage employee mental health benefit enrollment, care navigation, therapy session management, utilization reporting, and wellness program integration — enabling automated EAP benefit administration, member eligibility verification, session authorization, and outcomes tracking through Lyra's employer-sponsored mental health benefits platform. Enables AI agents to manage member eligibility for employee and dependent benefit enrollment verification automation, handle care navigation for therapy session booking and provider matching automation, access session management for authorized mental health session tracking and utilization automation, retrieve utilization reporting for aggregate benefit usage and ROI reporting automation, manage wellbeing check-in for employee wellness assessment and trend tracking automation, handle provider management for therapist network and availability management automation, access authorization for mental health session and service authorization automation, retrieve outcomes tracking for clinical outcome measure aggregation automation, manage population analytics for workforce mental health trend identification automation, and integrate Lyra with HRIS, benefits administration, and health plan systems for mental health benefit automation.

Evaluated Mar 07, 2026 (0d ago) vcurrent
Homepage ↗ Other lyra-health mental-health EAP behavioral-health employee-benefits digital-therapy
⚙ Agent Friendliness
46
/ 100
Can an agent use this?
🔒 Security
80
/ 100
Is it safe for agents?
⚡ Reliability
60
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
10
Documentation
58
Error Messages
56
Auth Simplicity
64
Rate Limits
52

🔒 Security

TLS Enforcement
99
Auth Strength
78
Scope Granularity
72
Dep. Hygiene
70
Secret Handling
78

Mental health benefits. HIPAA, SOC2, GDPR. OAuth2. US. Employee mental health and PHI data.

⚡ Reliability

Uptime/SLA
62
Version Stability
64
Breaking Changes
58
Error Recovery
58
AF Security Reliability

Best When

A large employer, health plan, or benefits administrator wanting AI agents to automate employee mental health benefit enrollment, session management, utilization tracking, and outcomes reporting through Lyra's employer-sponsored mental health benefits platform.

Avoid When

EMPLOYER CONTRACT REQUIRED: Lyra Health serves employers and health plans; automated public-developer assumption creates employer_agreement_required; automated must be Lyra Health employer client. PHI HANDLING REQUIRES BAA: Employee mental health data is protected PHI; automated generic-data assumption creates HIPAA_violation for mental health data processing without signed BAA; automated must execute BAA and implement HIPAA-compliant data handling. DE-IDENTIFIED ONLY FOR REPORTING: Lyra provides only aggregate, de-identified reporting to employers; automated individual-level assumption creates HIPAA_access_violation for attempts to access individual employee mental health data; automated must use only de-identified, aggregate reporting endpoints. MEMBER ELIGIBILITY DRIVES ACCESS: Only eligible employees and dependents can access Lyra benefits; automated universal-access assumption creates access_denied for members not enrolled in the employer's Lyra benefit; automated must verify eligibility before benefit interactions.

Use Cases

  • Automating employee mental health benefit eligibility verification for HR benefits automation agents
  • Managing mental health session utilization and reporting for benefits analytics automation agents
  • Integrating mental health benefit enrollment with HRIS changes for workforce automation agents
  • Reporting aggregate workforce mental health trends for employer population health agents

Not For

  • Direct patient clinical care (Lyra's API is for employer benefit administration, not direct clinical EHR integration)
  • Individual consumer mental health app development (Lyra serves employer-sponsored benefits, not direct-to-consumer apps)
  • International employee mental health benefits outside Lyra's network markets

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: oauth2
OAuth: Yes Scopes: Yes

Lyra Health uses OAuth2 for Mental Health Benefits REST API. REST API with JSON. Burlingame, CA HQ. Founded 2015 by David Ebersman (former Facebook CFO). Raised $910M+ (Coatue Management, General Atlantic). $4.6B+ valuation (2021). Products: Lyra Mental Health Benefit (employer EAP), Lyra Care Navigator, Lyra Coaching. 80+ enterprise clients including Starbucks, Facebook/Meta, Morgan Stanley, NVIDIA. Competes with Spring Health, Modern Health, and Brightside for employer-sponsored digital mental health benefits.

Pricing

Model: subscription
Free tier: No
Requires CC: No

Burlingame CA. $4.6B valuation. $910M raised. 80+ enterprise clients. Employer mental health benefits leader.

Agent Metadata

Pagination
page
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • ONLY AGGREGATE DATA IS AVAILABLE: Lyra only provides de-identified, aggregate population data to employers; automated individual-member assumption creates HIPAA_access_violation for attempts to retrieve individual employee mental health records; automated must only request and use aggregate reporting
  • ELIGIBILITY IS HR-DRIVEN: Employee eligibility in Lyra comes from HRIS feed; automated real-time assumption creates eligibility_lag for newly enrolled employees not yet reflected in Lyra eligibility due to HRIS sync delay; automated must account for eligibility sync latency
  • SESSION COUNTS ARE PLAN-SPECIFIC: Each employer's Lyra benefit has specific session count and service limits; automated universal-limit assumption creates authorization_exceeded for session requests beyond employer's contracted benefit levels; automated must query employer plan limits before session management
  • CARE DATA REQUIRES MEMBER CONSENT: Accessing any member care information requires member authorization; automated employer-blanket-access assumption creates unauthorized_access for member care data without explicit member consent; automated must handle consent requirements per HIPAA
  • REPORTING LATENCY EXISTS: Lyra aggregate reporting has processing latency; automated real-time-utilization assumption creates stale_data for utilization reports accessed immediately after benefit usage; automated must account for reporting latency in analytics workflows

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Lyra Health Mental Health Benefits REST API.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-07.

6470
Packages Evaluated
26150
Need Evaluation
173
Need Re-evaluation
Community Powered