DELETE
Unblock a user

Overview

Removes the directed block callerUserId → :userId. Because block is directed, calling unblock only removes the row the caller created. If the other user has also blocked the caller, that other block remains and areBlockedEither still returns true — so the chat surface stays sealed from the caller’s perspective. The endpoint is idempotent: calling unblock when no block exists is a no-op and returns unblocked: false. The status code is still 200 — the resource is in the desired state.

Authentication

Bearer <accessToken> required. requireOnboarded middleware applied.

Path parameters

Query parameters

None.

Request body

None.

Response — 200 OK

Example response (block removed)

Example response (no-op — no block existed)

Error responses

Side effects

  • If a blocks row existed for (caller, :userId), it is deleted.
  • Future contact between the two users is permitted only if there is no remaining block in either direction.
Unblocking does NOT automatically re-open a previously-closed conversation. If the conversation was created before either block, it still exists and status is unchanged; the gates simply stop firing.

See also

curl