Delete a federation peer
DELETE /admin/federation/peers/{id}
Deletes a peer from your peer list at once, together with the local records tied to it. Nothing is sent to the peer, and there’s no undo.
The database removes, along with the peer: your shares to it, all of its outbox and inbox rows whatever their state, suggestions saved from its public list, the accounts cached from it, and the comments and likes its users left here, together with any replies to those comments. Your activity history and audit log keep their entries. Adding the peer again starts a new, empty record.
The peer isn’t told: no aa:Unshare is sent, and it keeps whatever
it already received. No audit event records the deletion. A delivery
already in progress can still reach the peer. As shipped, the
outbox’s in-memory list of recipients for each post isn’t cleared,
so new activity about a post that was shared with this peer can stop
outgoing delivery until the app restarts.
This is also how you refuse a pending pairing request. GET /admin/federation/peers/{id}/defederation-preview gives some of the
counts first. An unknown id gets 404. Needs the system.admin
capability.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Responses
Section titled “ Responses ”Peer removed.
Authentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}Authenticated but missing required capabilities
object
Human-readable error summary
Example
the request could not be completedResource not found
object
Human-readable error summary
Example
the request could not be completed