Monitoring send health

WUTS derives a send-health signal for each device (WhatsApp instance) from its real send outcomes over the last 24 hours. Use it to detect when WhatsApp is restricting your number for new contacts — the reach-out time-lock — before it silently kills your delivery.

Every request below is authenticated with your tenant token (Authorization: Bearer <token>). See Authentication for how to obtain it.

The endpoint

GET /devices/{deviceID}/send-health

curl -H "Authorization: Bearer $WUTS_TOKEN" \
  https://api.wuts.com.br/devices/DEVICE_ID/send-health

{
  "success": true,
  "health": {
    "device_id": "d3f1a2b4-7c6e-4f01-9a2b-1c2d3e4f5a6b",
    "window_hours": 24,
    "sent_ok": 128,
    "reachout_blocked": 0,
    "other_errors": 0,
    "total": 128,
    "block_rate": 0,
    "restricted": false,
    "restriction": "",
    "available": true
  }
}

Interpreting the result

• Healthy — restricted: false and available: true: sending normally.
• Restricted — restricted: true: WhatsApp is blocking messages to people who have not messaged you first. Common on new or recently re-created numbers.
• No data — available: false: nothing sent in the window yet.

What to do when restricted

The reach-out time-lock is enforced by WhatsApp, not by WUTS — no API call removes it. To recover:

1. Ask recipients to send the first message (or reply) — warm conversations are not blocked.
2. Reduce volume and avoid bulk cold outreach; let the number age.
3. Use a clean, aged number that was never banned for outbound campaigns.
4. For proactive notifications, prefer an opt-in flow where the customer initiates the conversation.

Polling

Poll every few minutes per active instance and alert when restricted flips to true. The window is rolling (24 h) and self-clears once the number recovers and resumes healthy sends.