Overview
Webhooks allow you to receive HTTP POST requests when specific events occur in your MedStrato organization. Use webhooks to:- Sync KOL data to your CRM in real-time
- Trigger workflows when campaigns are sent
- Update external systems when event RSVPs change
- Monitor regulatory signals as they arrive
Setting Up Webhooks
1. Create a Webhook Endpoint
Create an endpoint in your application that accepts POST requests:2. Register Your Webhook
Webhook Events
KOL Events
| Event | Description |
|---|---|
kol.created | A new KOL was added |
kol.updated | A KOL profile was updated |
kol.archived | A KOL was archived |
kol.tier_changed | A KOL’s tier was changed |
Event Events
| Event | Description |
|---|---|
event.created | A new event was created |
event.updated | An event was updated |
event.cancelled | An event was cancelled |
event.attendee_added | An attendee was added |
event.rsvp_updated | An RSVP status changed |
Campaign Events
| Event | Description |
|---|---|
campaign.created | A new campaign was created |
campaign.sent | A campaign was sent |
campaign.email_opened | A recipient opened an email |
campaign.link_clicked | A recipient clicked a link |
Signal Events
| Event | Description |
|---|---|
signal.new | A new regulatory signal was detected |
signal.high_impact | A high/critical impact signal was detected |
Webhook Payload
All webhook payloads follow this structure:Verifying Signatures
MedStrato signs all webhook payloads using HMAC-SHA256. Verify signatures to ensure requests are authentic:Retry Policy
If your endpoint returns a non-2xx status code, MedStrato will retry the webhook:| Attempt | Delay |
|---|---|
| 1st retry | 1 minute |
| 2nd retry | 5 minutes |
| 3rd retry | 30 minutes |
| 4th retry | 2 hours |
| 5th retry | 24 hours |