HealthWorkforce IQ/API/Market Data API
API-first market signals

Live healthcare labor market data — delivered via API

Continuous job, pay, and market-pressure signals designed for systems, models, and decision engines.

Usage-based and enterprise licensing available.
Who this API is for

Built for API buyers embedding market context into products and systems

Workforce technology platforms
VMS, ATS, ERP — enrich pricing, routing, and staffing logic with live context.
Internal pricing & analytics teams
Standardize benchmarks, monitor drift, and quantify exposure across markets.
Data science & economic modeling
Inject fresh signals at inference time to reduce decision error and bias.
Healthcare staffing marketplaces
Improve matching and pricing with demand, compensation, and pressure signals.
Enterprise finance / ops systems
Bring market benchmarks into planning, budgeting, and controls.
What data you get

Data products you can call from pricing, workforce, and decision systems

Job Demand Signals
  • Active demand by role, location, specialty
  • Velocity and spike detection
  • Demand trend deltas (7d / 30d)
Compensation & Rate Signals
  • Market ranges (P25 / P50 / P75)
  • Differentials and premiums
  • Contract vs staff indicators
Market Pressure Indicators
  • Supply–demand imbalance
  • Regional heat
  • Drift detection
You’re buying outputs — not pipelines. Each endpoint returns versioned, time-stamped market context with coverage and confidence to support enterprise decisioning.
Moat

Inference-Time Market Context

Market data is injected at request time — not precomputed — ensuring outputs reflect current conditions.

Live context at request time
Fresh demand, pay, and pressure signals attached to each call.
Drift-aware responses
Signals include drift indicators and confidence so your systems can act safely.
Graceful degradation
When signals weaken, responses downshift with transparency instead of failing silently.
Sample responses

See the outputs your systems will ingest

Example response — Job demand signals
Sample request
GET /v1/market/demand?role=RN&specialty=ICU&location=Chicago%2C%20IL
Authorization: Bearer <token>
Accept: application/json
Example response
{
  "as_of": "2026-01-13T14:22:10Z",
  "request": {
    "role": "Registered Nurse",
    "specialty": "ICU",
    "location": "Chicago, IL"
  },
  "signals": {
    "active_demand": {
      "postings": 1243,
      "change_7d_pct": 6.1
    },
    "velocity": {
      "time_to_fill_index": 1.18,
      "spike_detected": true,
      "spike_score": 0.72
    },
    "market_pressure": {
      "pressure_index": 0.81,
      "supply_demand_imbalance": 0.27,
      "regional_heat": "high"
    }
  },
  "coverage": {
    "geography": "metro",
    "confidence": "high"
  },
  "version": "2026-01-01"
}
Example response — Compensation & rate ranges
Sample request
GET /v1/market/compensation?role=CNA&location=Phoenix%2C%20AZ&employment_type=contract
Authorization: Bearer <token>
Accept: application/json
Example response
{
  "as_of": "2026-01-13T14:22:10Z",
  "request": {
    "role": "CNA",
    "location": "Phoenix, AZ",
    "employment_type": "contract"
  },
  "ranges": {
    "hourly": {
      "p25": 22.75,
      "p50": 26.5,
      "p75": 31.25
    },
    "differentials": {
      "night_shift_premium_pct": 9.5,
      "weekend_premium_pct": 7.2
    },
    "contract_vs_staff_indicator": "contract_premium"
  },
  "market_notes": {
    "drift_detected": true,
    "drivers": [
      "seasonal demand",
      "regional vacancy pressure"
    ]
  },
  "coverage": {
    "geography": "metro",
    "confidence": "medium"
  },
  "version": "2026-01-01"
}
API characteristics

Enterprise-grade expectations, stated clearly

Latency targets
Sub-second typical; tiered options available
Update cadence
Continuous signals with time-stamped outputs
Versioning policy
Versioned endpoints + changelog discipline
Uptime SLA
Contracted SLA for enterprise tiers
Freshness guarantees
As-of timestamps and confidence on every response
Clarification

What this is not

This API provides market context and signals. For embedded UI, workflows, and end-user decisioning, see White-Label Partners.

Request access

Get API access and coverage details

We’ll confirm geography and role coverage, share sample endpoints, and align on expected volume.

Request API access
Get keys, docs, and sandbox options.
Discuss data coverage
Markets, roles, specialties, freshness.
View sample responses
Validate schema and confidence signals.
Request API access
A few fields help us route you and prepare coverage details.
Reviewed by our team. Response within 1 business day with next steps and documentation.