WhatsApp outreach data#
The doctors API can seed a review queue for a lawful outreach workflow:
GET /api/v1/doctors?country=es&city=madrid&whatsapp=true&limit=100
The filter means only that Doctosan's published source data identifies the primary phone as mobile or otherwise technically WhatsApp-reachable. It does not mean the practice opted in to marketing, agreed to a particular sender, or is eligible under the laws that apply to you.
Recommended CRM boundary#
Store imported directory evidence separately from outreach decisions:
| Field | Source |
|---|---|
doctosanDoctorId |
Doctor id; use for import deduplication and refreshes. |
publishedPhone |
Current API phone. |
whatsappReachability |
Current API whatsappEligible. |
sourceProfileUrl |
Current API profileUrl. |
legalBasis, consent, suppression |
Your own reviewed compliance records; never derive these from Doctosan. |
lastSyncedAt |
Your import timestamp. |
Before each message, the outreach system should independently check its own suppression list, jurisdiction, purpose, sender identity, message template, frequency limits, and WhatsApp Business policy obligations.
Reachability is not consent
Never map
whatsappEligible: truetoconsent: true,optedIn: true, or an automatic send. Keep a human or an independently justified compliance gate between directory import and first contact.
Refresh and deletion#
Directory records change. Refresh candidates by stable id, and stop using a
record if GET /api/v1/doctors/{doctorId} returns 404. A CRM suppression
record should outlive a directory deletion so a removed contact is not
re-imported later under a new listing.