Send the consent request again
The old link dies. Refused when consent was already given and is not due for renewal — revoke first if it truly must be asked again.
BearerAuthorizationBearer <JWT>uid*string1 <= lengthapplication/json- body
reason*string3 <= length <= 200Sent
application/json- response
success*truetruedata*curl -X POST 'http://localhost:3000/admin/seats/string/consent/resend' \ -H 'Content-Type: application/json' \ -d '{ "reason": "string"}'{ "success": true, "data": { "ok": true }}Every request and where it stands GET
Two views of one list. `sort=recent` (default): every request, superseded ones included, newest first. `sort=severity` or any `state`: the problem QUEUE — one row per live seat (its newest request), vencido > expirado > pendente > recusado > revogado > dado, then longest in the state first, with `stateSince` for "No estado há". `counts` are per state over the queue, within `account`. No name: the account and an age band are enough to triage.
Drop the session so it can be paired again POST
Ends the live pairing at the provider. The dependent has to scan again, so the reason is required and kept — this is the most disruptive thing an operator can do to a family.