---
title: "Block a support contact"
method: POST
path: "/v1/support/conversations/{conversation}/block"
tags: ["Support Inbox"]
---

# Block a support contact

`POST /v1/support/conversations/{conversation}/block`

## Request

- Base URL: `https://api.subscriby.net`
- URL: `https://api.subscriby.net/v1/support/conversations/{conversation}/block`
- Auth: HTTP bearer

```bash
curl -X POST https://api.subscriby.net/v1/support/conversations/$CONVERSATION_ID/block \
  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)"
```

Silences the member behind the thread: their messages to this project's bot are dropped without any notice to them, and the thread cannot reopen on inbound. Their paid access is untouched, because a block is an inbox decision and not a moderation one; use the [Members](https://docs.subscriby.net/api/v1/reference/members) endpoints to ban or kick. Idempotent and answers `200` with the thread; blocking an already-blocked contact changes nothing and emits nothing, and when the block actually flips `support.conversation.blocked` fires once.

## Path parameters

- `conversation` string, uuid, required

## Headers

- `Idempotency-Key` string, uuid, required

## Response `200`

The thread, blocked.

- object
  - `data` SupportConversationResource, required: A support conversation: the one durable thread between a project and a member on one connector.
    - `id` string, required: The conversation's id.
    - `project_id` string, required: The project whose bot the member wrote to.
    - `subscriber_id` string, required: The member behind the thread; may be a `lead` who never paid, since anyone who can reach the bot can open a conversation.
    - `member_name` string, required: The member's display name, or "Unknown member" when they have not shared one, so a picker has something human to show.
    - `channel` string, required: The key of the connector the member wrote through. A member who writes through two connectors has two conversations, and each reply goes back on the connector its conversation came in on.
    - `status` string, required: `open`, `pending`, `snoozed` or `resolved`.
    - `assigned_to_user_id` string, nullable, required: The team member the thread is assigned to; null when unassigned.
    - `subject` string, nullable, required: A subject line, when the inbox set one; null otherwise.
    - `unread_count` integer, required: How many inbound messages the team has not read.
    - `blocked` boolean, required: True when inbound messages from the member are being dropped: the thread is history only and cannot reopen on inbound.
    - `last_message_at` string, nullable, required: When the newest message, either way, arrived, ISO 8601.
    - `last_inbound_at` string, nullable, required: When the member last wrote, ISO 8601; null if never.
    - `last_outbound_at` string, nullable, required: When the team last replied, ISO 8601; null if never.
    - `first_response_at` string, nullable, required: Stamped **once**, on the first human reply ever in the thread: an SLA measure of how long the member waited for a person, not of the most recent reply. A reopen does not reset it.
    - `resolved_at` string, nullable, required: When the thread was last resolved, ISO 8601; null while open.
    - `created_at` string, nullable, required: When the thread opened, ISO 8601.
    - `updated_at` string, nullable, required: When the thread last changed, ISO 8601.

## Other responses

- `400`: `IDEMPOTENCY_KEY_MISSING`: every write needs an `Idempotency-Key` header. Send a fresh UUID per distinct operation.
- `401`: `AUTHENTICATION_REQUIRED`: the request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an `sbt_test_` token on production).
- `403`: `TOKEN_MISSING_ABILITY`: the token is valid but does not carry the ability this endpoint requires; `error.context.required_ability` names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers `FORBIDDEN`, `TEAM_TIER_REQUIRED` or `CONNECTOR_TIER_REQUIRED` with the same status, and says so in its own description.
- `404`: `RESOURCE_NOT_FOUND`: an id in the path names nothing the token can see. `TENANT_MISMATCH`: the project sits outside the token's `scope:project:` allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.
- `409`: `IDEMPOTENCY_KEY_REUSED`: the key was already used in the last 24 hours with a different request body.
- `425`: `IDEMPOTENCY_REPLAY_IN_PROGRESS`: the first request with this key is still running; retry in a few seconds and the original response is replayed.
- `429`: `RATE_LIMITED`: the token has spent its 300 requests a minute or 10,000 an hour; `Retry-After` says when the next one is accepted.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)