Skip to content

Unblock a user

DELETE
/users/{ref}/block

Removes your block of the account ref. A block they hold on you isn’t changed, and no follow comes back: to follow again, follow them again.

Any signed-in account can unblock. Without a session cookie or bearer token that identifies you, the answer is 401, whether or not public mode is on. A ref that isn’t a whole number gets a plain-text 400 before sign-in is checked. The account isn’t looked up, so a ref you haven’t blocked, one with no account and your own all get 204, including on a second request.

Each request, one that removes nothing included, records an undo in the activity log in the same step; nobody is notified. A block and an unblock of the same account sent at the same time can both succeed, and the order of their responses doesn’t tell you whether the block remains. Server errors get a plain-text 500.

ref
required
integer format: int64

The account’s ref.

The unblock request succeeded, also when there was no block to remove.

Authentication required, missing, or invalid

object
error
required

Human-readable error summary

string
Example
the request could not be completed
Example
{
"error": "authentication required: sign in and retry with a valid session or API token"
}