Skip to main content
POST
Remove Opt-Outs

Endpoint

This reverses only what the Opt-Outs API suppressed. A contact who replied STOP, tapped an unsubscribe button, turned marketing off in WhatsApp itself, or was uploaded through the Audience screen in Connectly stays suppressed. Those contacts are reported under notOptedOutCount and messages to them remain blocked.Your re-enable list is your own record of who consented with you. It is not evidence that someone who opted out on the channel changed their mind, so Connectly will not act on it as if it were.

Request body

entries array (required)

Each object names one WhatsApp contact to re-enable. Maximum 10,000 per request.
The same contact listed twice counts once.

Examples


Response

The API returns HTTP 200 with a data object. Counts are over the contacts you named. Success response
A large notOptedOutCount is normal and is not an error. If you send your full consented list every night, every contact you never suppressed through this API lands there.

Error responses

Unreadable entries are dropped and counted — they do not fail the batch. The request fails outright only when no entry survives. Rejection reasons are the same as Add opt-outs.

Rate limiting

This endpoint is limited to 60 requests per minute. Exceeding this returns HTTP 429 Too Many Requests.