support.conversation.unblocked

When this fires

A creator lifts the block on a support conversation:

Dashboard: Unblock member in the thread's header menu in the support inbox.
REST: POST /v1/support/conversations/{conversation}/unblock.
MCP: the unblock_support_contact tool.

It does not fire when:

The conversation was not blocked. Unblocking an unblocked thread writes nothing and emits nothing; the call is idempotent.
A banned member is unbanned. That is member.unbanned; a ban and a support block are independent, and lifting one does not touch the other.

Unblocking restores the flow of new messages. It does not replay anything the member sent while blocked; those messages were dropped at ingestion and are gone.

Caveats

The thread's status is unchanged by an unblock, exactly as it was by the block. A thread that was resolved when blocked is still resolved now; the member's next message will reopen it and raise support.conversation.reopened as usual.
Nothing is replayed. If the member wrote in while blocked, those messages produced no support.message.received and never will.
The payload does not say how long the block lasted. Pair this event's created_at with the matching support.conversation.blocked by conversation_id if you report on it.

Related events

support.conversation.blocked: the state this event reverses.
support.conversation.reopened: what the member's next message may now trigger.

Ability to subscribe

support-conversation:view

A token needs this to subscribe an endpoint to the event.

Header Parameters

SB-Signature*string

t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.

SB-Event-Id*string

The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.

SB-Event-Name*string

The event name, the same as the envelope's type.

Content-Type*string

Always application/json.

User-Agent*string

Always Subscriby-Webhooks/1.0.

Payload

JSONWhat Subscriby posts to your endpointapplication/json

The signed JSON envelope posted to your endpoint.

The envelope every event is delivered in.

id*string

A ULID unique to the event, prefixed evt_. Every retry carries the same id, so it is the key to deduplicate on.

type*"support.conversation.unblocked"

The event name, always support.conversation.unblocked here.

Value in

"support.conversation.unblocked"

created_at*string

When the event was emitted, server time, ISO 8601.

Formatdate-time

api_version*string

The contract version of the payload shape, 2026-05-01 today. A breaking change to a shape ships under a new version.

project_id*|

The project the event belongs to; null for team-scoped and billing events.

Formatuuid

data*

The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.

Responses

2XXAny success status

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

defaultAny other status

Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or POST /v1/webhook-deliveries/{delivery}/retry. After 20 consecutive failures the endpoint is paused until it is resumed.

Delivery to your endpoint

Subscriby sends this event as one HTTP request to every endpoint subscribed to it.

POSThttps://example.com/webhooks/subscribyyour endpoint URL

Headers

SB-Signature: t=1758636300,v1=5f1c…
SB-Event-Id: 01HXDELIVERY000000000TST
SB-Event-Name: support.conversation.unblocked
Content-Type: application/json
User-Agent: Subscriby-Webhooks/1.0

Body

{  "id": "evt_01HX...",  "type": "support.conversation.unblocked",  "created_at": "2026-09-06T11:05:00Z",  "api_version": "2026-05-01",  "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",  "data": {    "conversation_id": "9e042b6f-5d81-4c37-a920-7b3e18cf6d45",    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",    "subscriber_id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80"  }}

Type definitions

The shapes above as types, ready to paste into your client.

export interface Body {  id: string;  type: "support.conversation.unblocked";  created_at: string;  api_version: string;  project_id: string | null;  data: Data;}export interface Data {  conversation_id: string;  project_id: string;  subscriber_id: string;}

When it arrives

Verify the signatureCheck the SB-Signature header before trusting anything in the body.Answer 2xx within 30 secondsAny other answer, or none, and Subscriby retries the delivery.

De-duplicate on SB-Event-IdA retry carries the same id as the first attempt.