Block a handle
Block a registered Relay Handle.
In a direct Chat, a block in either direction stops delivery. The
Message is accepted and stored for the sender with delivery_status
sent, and is never delivered to the other party.
In a group Chat, blocking is one way. Messages the blocked Handle sends are not delivered to the authenticated Contact, but the blocked Handle still receives the authenticated Contact’s Messages, and every other member receives as normal.
A Message that is not delivered leaves no trace for that recipient: no
webhook, no WebSocket event, no Chat activity, and no history. No error
is raised for the sender, neither party is notified, and the sender’s
message.delivered fires when at least one recipient was delivered.
Blocking does not delete existing Chats or history. It only stops new traffic.
Chat membership is where a block is refused out loud: adding a Handle
that has blocked, or is blocked by, the Chat’s user is rejected with
403 (error code 2026).
reason is a free-text note returned on the list endpoint. Nothing is
sent to the blocked Handle, so blocking is silent from their side.
Authorizations
Bearer token authentication. Include your API token in the Authorization header.
Format: Authorization: Bearer <your-token>
Body
Response
Handle blocked successfully

