curl --request POST \
  --url https://{projectID}.texterchat.com/server/api/v2/quick-replies \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "send": {
    "contents": [
      {
        "type": "text",
        "text": "Thanks for reaching out! An agent will reply shortly."
      }
    ],
    "target": [
      {
        "name": "whatsapp",
        "accountId": "972586640430"
      }
    ]
  },
  "display": {
    "position": "top",
    "title": "Greeting"
  }
}
'

{
  "_id": "<string>",
  "send": {
    "contents": [
      {}
    ],
    "betweenMessagesDelay": 123,
    "target": [
      {
        "accountId": "<string>",
        "id": "<string>"
      }
    ]
  },
  "display": {
    "title": "<string>",
    "note": "<string>",
    "departments": [
      "<string>"
    ],
    "users": [
      "<string>"
    ]
  },
  "metadata": {
    "created": 123,
    "updated": 123,
    "client": {}
  }
}

Quick Replies

Create Quick Reply

Create a new quick reply. A quick reply holds one or more prepared messages (send.contents, same structure as Send a Message to Chat bodies) and a send.target list defining which channels - or which single chat - it is available for. The contents are validated against the limits of every targeted channel.

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):

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".
Mark it with the Update Existing Quick Reply endpoint: [{ "updateClientMetadata": { "aiQuickReply": true } }].
When the suggestion becomes stale, delete it (or replace its contents with updateSendContents).

See the “AI suggested reply (step 1 of 2)” request example.

POST

quick-replies

curl --request POST \
  --url https://{projectID}.texterchat.com/server/api/v2/quick-replies \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "send": {
    "contents": [
      {
        "type": "text",
        "text": "Thanks for reaching out! An agent will reply shortly."
      }
    ],
    "target": [
      {
        "name": "whatsapp",
        "accountId": "972586640430"
      }
    ]
  },
  "display": {
    "position": "top",
    "title": "Greeting"
  }
}
'

{
  "_id": "<string>",
  "send": {
    "contents": [
      {}
    ],
    "betweenMessagesDelay": 123,
    "target": [
      {
        "accountId": "<string>",
        "id": "<string>"
      }
    ]
  },
  "display": {
    "title": "<string>",
    "note": "<string>",
    "departments": [
      "<string>"
    ],
    "users": [
      "<string>"
    ]
  },
  "metadata": {
    "created": 123,
    "updated": 123,
    "client": {}
  }
}

הרשאות

Authorization

string

header

נדרש

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.

גוף

application/json

send

object

נדרש

Show child attributes

display

object

How and where the quick reply is displayed in Texter

Show child attributes

תגובה

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

Show child attributes

display

object

How and where the quick reply is displayed in Texter

Show child attributes

metadata

object

Show child attributes

Get Existing Quick Replies Delete Quick Reply