Typing Indicatorsv2

Stop typing indicator

DELETE/chats/{chatId}/typing

Stop the typing indicator for a chat. Works for both 1:1 chats (pass a phone number or email as chatId) and group chats (pass the group ID, e.g. grp_...).

RCS limitation: typing indicators are only delivered for iMessage chats — the RCS protocol does not carry composing state. Calls against RCS-routed chats return 200 with a warning field and have no visible effect on the recipient.

Path parameters

chatIdRequiredstring

Chat identifier. Can be: (1) phone number in E.164 format (e.g., +15551234567), (2) email address, (3) group ID (grp_xxxx), or (4) comma-separated list of phone numbers/emails for multi-recipient group chats (e.g., +15551234567,+15559876543). All values should be URL-encoded.

Headers

AuthorizationRequiredstring

Your API key, sent as a bearer token: Authorization: Bearer <api_key>. Editing this stays in sync with the API key box on the right.

Bearer

Returns

chat_idoptionalstring

Chat identifier

typingoptionalboolean

Whether typing indicator is active

started_atoptionalinteger

Timestamp when typing started (only for start)

stopped_atoptionalinteger

Timestamp when typing stopped (only for stop)

warningoptionalstring

Present when the request was accepted but the indicator could not be delivered. The most common reason is that the chat last routed via RCS, which does not carry composing state.

Response codes

200Typing indicator stopped

400Invalid request parameters

401Authentication required or invalid

502Temporary communication error

503No active number available

Sends a live request with your values and shows the real response below. Your key is stored only in this browser.

Request

curl -X DELETE https://api.blooio.com/v2/api/chats/chat_a1b2c3d4/typing \  -H "Authorization: Bearer bl_live_..."

Response objectexample

{  "chat_id": "chat_a1b2c3d4",  "typing": false,  "started_at": 0,  "stopped_at": 0,  "warning": "RCS chats do not support composing indicators"}