Webhooks
Inbound webhooks GuideLab receives from third‑party services.
GuideLab exposes a small number of inbound webhook endpoints under
/webhooks. These are called by external services — they are not events that
GuideLab sends to your servers. Each is verified against the provider's
signature and is therefore public (no GuideLab session required).
Endpoints
| Method | Path | Source |
|---|---|---|
POST | /webhooks/stripe-connect | Stripe Connect — payment & account events |
POST | /webhooks/medit | Medit — scanner / case events |
See the Webhooks section of the API reference for the full payloads and responses.
Stripe Connect
POST /webhooks/stripe-connect receives Stripe Connect
events (payments, payouts, and connected‑account updates) and reconciles them
with GuideLab's finance records. Stripe signs each request; GuideLab verifies the
signature before processing.
Medit
POST /webhooks/medit receives events from the Medit
scanner integration, used to ingest scan data into the relevant case.
These endpoints are configured in the respective provider dashboards to point at
https://api.guidelab.co/webhooks/…. You don't call them directly — they're
documented here so the behaviour of the integration is transparent.