---
title: "Block Relationship"
method: POST
path: "/api/connections/blocks"
tags: ["connections"]
---

# Block Relationship

`POST /api/connections/blocks`

## Request

- Base URL: `https://app.thinqos.com` (the document declares no server; this is the origin it was published from)
- URL: `https://app.thinqos.com/api/connections/blocks`
- Auth: none declared

Freeze the relationship with another identity: no new traffic either way.

Existing conversations and their history stay exactly where they are and
stay readable - this stops what happens next, it does not erase what
happened. Reversible with ``DELETE /api/connections/blocks/{id}``, which
only the blocker may call.

## Headers

- `x-impersonate-identity-id` string, nullable

## Request body

- RelationshipBlockBody
  - `other_identity_id` string, uuid, required

## Response `201`

Successful Response

- RelationshipBlockResponse: One frozen relationship, from the calling identity's point of view. ``blocked_by_identity_id`` is the whole payload's reason for existing: only the identity that placed a block may lift it, so a caller cannot render a working Unblock control from a bare boolean.
  - `other_identity_id` string, uuid, required
  - `blocked_by_identity_id` string, uuid, required
  - `blocked_at` string, date-time, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/thinqos/apis/thinqos-api.md) · [All operations](https://skmtc.dev/thinqos/apis/thinqos-api/llms.txt) · [OpenAPI document](https://skmtc.dev/thinqos/apis/thinqos-api/revisions/5fdd1072e877?raw)