Integration Ports
Public-facing integration surface for Lemonaid's marketing stack — Project Stitch
Project Stitch · Lemonaid Integration Surface
FWD Care runs independently of Bask.
Every data point that moves through Bask is mirrored into our own Supabase store via the webhook receiver below. Lemonaid's marketing stack connects here — not to Bask directly. That means attribution, patient journeys, and content APIs are all ours to control and expose at any speed.
Bask Webhook Receiver
Livehttps://portal.fwd.care/api/webhooks/baskReceives all 17 Bask event types. Writes to bask_event_log (audit) + typed table per event. HMAC-verified via X-Bask-Signature header.
Supported event types (17):
To activate: In Bask portal → Settings → Webhooks → set destination URL to the endpoint above. Already active for 11 of 17 event types.
Health Check
Livehttps://portal.fwd.care/api/healthReturns 200 JSON with service status, Supabase reachability, and timestamp. Suitable for uptime monitoring by Lemonaid.
Attribution Parameter Surface
Ready to wire| UTM Parameter | FWD Care Field | Notes |
|---|---|---|
| utm_source | signUpSearchParams.utm_source | Lemonaid ad network or email |
| utm_medium | signUpSearchParams.utm_medium | paid_social | email | organic |
| utm_campaign | signUpSearchParams.utm_campaign | Lemonaid campaign name |
| utm_content | signUpSearchParams.utm_content | Creative variant |
| utm_term | signUpSearchParams.utm_term | Keyword if applicable |
| fwd_ref | signUpCookies.fwd_ref | FWD Care internal referral token |
| lemon_ref | signUpCookies.lemon_ref | Lemonaid cross-brand referral |
Bask surfaces signUpSearchParams and signUpCookies on newPatient and newOrder events. These land in the typed tables above and are queryable for attribution reporting.
Peptide Catalog / Content-Feed API
Planned — Phase 2https://portal.fwd.care/api/catalogJSON feed of all peptide_catalog rows. Intended for Lemonaid's content team to pull FWD Care molecule status, notes, and readiness into their CMS.
https://portal.fwd.care/api/catalog/[slug]Single molecule detail, including status, molecule, category, signal notes, and ready_for_market flag.
MD Integrations (MDI) — Clinical Data
Planned — Phase 2MDI API (985-page reference in research/md-integrations-endpoint-index.txt) provides case creation, Rx status, and provider assignment. Once wired, patient events from MDI surface on the patient timeline at /patients/[id].
Env vars needed: MDI_CLIENT_ID + MDI_CLIENT_SECRET
HubSpot CRM Sync
Connected — not yet wiredHubSpot connector is live (Vercel integration). Patient CRM events will sync to HubSpot contacts once the identity-linking job is wired. FWD Care patient IDs → HubSpot contact IDs will be stored in patient_identity with source = 'hubspot'.