Skip to main content
POST
Required token scopes: Manage quick replies

AI quick replies

Texter’s inbox shows a special AI suggestion UI for quick replies whose metadata.client.aiQuickReply is true: they appear as suggested replies on the targeted chat, sorted on top, with an “unseen suggestion” indicator for agents. To create one (the same flow Texter’s own AI assistant uses):
  1. Create a quick reply targeted at one specific chat - set send.target[0].id to the chat ID (the chat’s _id, from Search Chats), and optionally display.note to something like "AI suggestion".
  2. Mark it with the Update Existing Quick Reply endpoint: [{ "updateClientMetadata": { "aiQuickReply": true } }].
  3. When the suggestion becomes stale, delete it (or replace its contents with updateSendContents).
See the “AI suggested reply (step 1 of 2)” request example.

Authorizations

Authorization
string
header
required

API token generated in Texter: gear icon → Developers → API Tokens. When creating a token, assign it the scopes required by the endpoints you plan to call - each endpoint lists its required scopes.

Body

application/json
send
object
required
display
object

How and where the quick reply is displayed in Texter

Response

The created quick reply. Field-by-field reference: The Quick Reply object

A quick reply - one or more prepared messages agents (or the AI assistant) can send into matching chats

_id
string

Unique identifier of the quick reply

send
object
display
object

How and where the quick reply is displayed in Texter

metadata
object