Junction API
Lab results and wearable data platform — auth, resources, and GHL integration.
| Property | Value |
|---|---|
| Base URL | https://api.us.junction.com |
| Auth | X-Vital-API-Key: <JUNCTION_API_KEY> |
| Environment | Production / US |
| Key prefix | pk_us_ = production, sk_ = sandbox |
Resource Areas
| Area | What's available |
|---|---|
| Users | Client accounts, demographics, user_id |
| Lab Testing | Lab orders, results, providers |
| Device / Wearable | Activity, sleep, body, heart rate summaries |
| Link | Connect clients to lab providers |
| Sense | Analytics and health insights |
| Webhooks | Event-driven triggers (e.g. lab_results.completed) |
GHL Integration
The contact.user_id custom field in GHL stores the Junction user_id, linking a client across both platforms. This is the primary cross-system identifier.
Planned Webhook
When Junction fires lab_results.completed, this endpoint will auto-trigger the pipeline:
POST /api/pipeline/webhook/junction // Payload includes user_id which maps to GHL contact.user_id // Pipeline auto-starts — no manual upload needed