Start typing indicator
/chats/{chatId}/typingStart the typing indicator for a chat. The indicator shows the recipient that you are typing. Works for both 1:1 chats (pass a phone number or email as chatId) and group chats (pass the group ID, e.g. grp_...); in a group every participant sees the indicator.
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
chatIdRequiredstringChat 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
AuthorizationRequiredstringYour API key, sent as a bearer token: Authorization: Bearer <api_key>. Editing this stays in sync with the API key box on the right.
Returns
chat_idoptionalstringChat identifier
typingoptionalbooleanWhether typing indicator is active
started_atoptionalintegerTimestamp when typing started (only for start)
stopped_atoptionalintegerTimestamp when typing stopped (only for stop)
warningoptionalstringPresent 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
Sends a live request with your values and shows the real response below. Your key is stored only in this browser.
curl -X POST https://api.blooio.com/v2/api/chats/chat_a1b2c3d4/typing \ -H "Authorization: Bearer bl_live_..."{ "chat_id": "chat_a1b2c3d4", "typing": false, "started_at": 0, "stopped_at": 0, "warning": "RCS chats do not support composing indicators"}