POST /registry/deregisterRemoves the session from every namespace and drops its record, so no new placements land on it. Its existing rows are not deleted; release them first. Rows left behind re-place on their next request (dead-owner eviction).
Authentication
pinboard:worker scope, same account that registered the session; the claim must cover the whole registration.
Request body
application/json, at most 1 MiB.
| Field | Type | Required | Description |
|---|---|---|---|
sessionId | string | Yes | Session to end. |
Example
curl -X POST https://pinboard.example.com/registry/deregister \
-H "Authorization: Bearer $PINBOARD_WORKER_TOKEN" \
-H "Content-Type: application/json" \
-d '{"sessionId": "3f9c0d6e2b1a4c7d8e9f0a1b2c3d4e5f"}'Response
200
Empty object.
{}Errors
| Status | Body | When |
|---|---|---|
401 | {"error":"unauthorized"} | No accepted credential |
403 | {"error":"forbidden"} | Missing scope, another account's session, or the claim no longer covers the registration |
503 | {"error":"not the serving fleet"} | Node not serving |
413 / 400 | body too large / invalid json | |
400 | {"error":"expected { sessionId }"} | Schema failure |
409 | {"error":"unknown session","reregister":true} | Session unknown or already expired |
A 409 here means the session is already gone; treat it as done.