SuperdindaDocs
Consents

Stop protection (public)

POST
/consent-requests/{token}/stop

Ends monitoring for the seat through stopMonitoring(seat, { kind: "dependent" }): an open-ended stop only a new consent lifts, the seat's key destroyed (stored messages and alert excerpts become unreadable), unread analysis windows dropped, imports failed, the WhatsApp session logged out. The consent becomes revoked by the dependent, and every guardian of the account is told the fact and the time — never a reason (event seat.stopped { cause: "dependent" }, notification consent.stopped). A new link cannot be sent for CONSENT_RESEND_COOLDOWN_HOURS. Idempotent: stopping again answers the first stop. token is either the consent link token or the stop link token (protectionLink, returned when consent is given). Either works while its consent is the seat's current one. Limits: reading RATE_CONSENT_READ_PER_LINK / _PER_IP (default 120 and 600 per 10 min), stopping RATE_CONSENT_WRITE_PER_LINK / _PER_IP (default 10 and 30 per hour) — shared with decline.

Path Parameters

token*string

the opaque token from the link

Length16 <= length <= 4096

Request Body

application/json
  1. body
confirm*true

the dependent confirmed they want protection to stop

Value intrue

Response Body

Stopped

application/json
  1. response
success*true
Value intrue
data*
Example Request
curl -X POST 'http://localhost:3000/consent-requests/stringstringstri/stop' \  -H 'Content-Type: application/json' \  -d '{  "confirm": true}'
Example Response
{  "success": true,  "data": {    "status": "stopped",    "at": "2019-08-24T14:15:22Z"  }}