Unfollow a user
DELETE /users/{ref}/follow
Removes your follow of the account ref. Their follow of you, if
they have one, isn’t changed.
Any signed-in account can unfollow. 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 and nothing else is checked, so a ref you don’t follow, one
with no account and your own all get 204, including on a second
request.
Once the follow is gone, the person’s posts shared with followers
only stop being readable to you, and this follow no longer brings
their posts into the following feed of GET /posts. A post you
can still read stays in that feed if it is filed under a team you
follow or carries a tag you follow, and anything you can read for
another reason stays readable.
Each request, one that removes nothing included, records an undo in the activity log in the same step; nobody is notified. A follow and an unfollow of the same account sent at the same time can both succeed, and the order of their responses doesn’t tell you whether the follow remains. Server errors get a plain-text 500.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The account’s ref.
Responses
Section titled “ Responses ”The unfollow request succeeded, also when there was no follow to remove.
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"}