Typing Indicators

Typing indicators show recipients that someone is actively composing a message. They create a more natural, real-time feel in conversations.

Start a typing indicator in a chat to show the recipient that you’re composing a message:

curl -X POST https://api.linqapp.com/api/partner/v3/chats/{chatId}/typing \
  -H "Authorization: Bearer $LINQ_API_KEY"

await client.chats.typing.start({chatId});

client.chats.typing.start({chat_id})

client.Chats.Typing.Start(context.TODO(), {chatId})

Stop the indicator when you’re done (it also clears automatically when you send a message):

curl -X DELETE https://api.linqapp.com/api/partner/v3/chats/{chatId}/typing \
  -H "Authorization: Bearer $LINQ_API_KEY"

await client.chats.typing.stop({chatId});

client.chats.typing.stop({chat_id})

client.Chats.Typing.Stop(context.TODO(), {chatId})

Tip: Send a typing indicator before your application processes a response (e.g., while an AI agent generates a reply). This gives the recipient a natural “someone is typing” experience. The indicator automatically clears when you send the actual message.

Subscribe to typing indicator webhooks to know when a recipient is typing:

See Webhooks for setup instructions and the Webhook Events API Reference for payload schemas.

• iMessage only — Typing indicators are an iMessage feature and are not available on RCS or SMS. See Protocol Selection for protocol capabilities.
• One-to-one chats only — Typing indicators are not supported in group chats. They only work in one-to-one conversations.
• Auto-clear — Typing indicators automatically clear when you send a message to the chat.
• Timeout — Typing indicators expire after approximately 60 seconds if not refreshed or stopped.
• Best-effort delivery — A 204 response means the request was accepted, not that the indicator was delivered. The chat must have had activity within the last 5 minutes for the indicator to reach the recipient.

See the Chats API Reference for the full typing indicator endpoint specification.