`POST /api/v1/pools/{name}/restore` — put a covered pool's members back.
const url = 'https://example.com/api/v1/pools/example/restore';const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/api/v1/pools/example/restore \ --header 'Authorization: Bearer <token>'Each member returns to its own recorded assignment, which for an inheriting node means no assignment at all. Restoring them all to the pool’s name would pin rows that were never pinned, leaving a deployment the takeover never promised to be reversible about.
A member whose pool a person has since changed by hand keeps that change — a later human decision outranks this bookkeeping — but its record is dropped either way, so a pool cannot stay marked as covered forever.
Restoring is deliberately not automatic when the site’s poller returns: 22 nodes moving on their own the moment a link comes back is its own surprise (ADR-107 Inc.4, out of scope).
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The pool that was being covered for
Responses
Section titled “Responses”How many nodes and folders went back
What one call re-pointed.
object
Folders re-pointed.
Nodes re-pointed.
Examplegenerated
{ "folders": 1, "nodes": 1}Not a usable pool name
Not signed in
ManageSystem required
No admin state