Skip to main content
POST
Create Saved Reply

Authorizations

Authorization
string
header
required

Your API key (ta_live_…) from Settings → API keys, sent as Authorization: Bearer <key>. Keep it on a server: it can message every customer you have. A key is full, build or read-only; a request its level does not allow is refused with 403.

Headers

Thinnest-Workspace
string

Developers only: the customer workspace this request acts in — its org_… id from POST /customers. Leave it out to act in your own workspace.

Example:

"org_3fKq9TzQ1mN8vB2xR7cLpA"

Body

application/json
shortcut
string
required

What a teammate types to find it. A leading / is dropped; up to 40 characters after that. Unique in the workspace, ignoring case.

Required string length: 1 - 40
Example:

"timings"

body
string
required

What the reply says, up to 2,000 characters. Trimmed.

Required string length: 1 - 2000
Example:

"We are open Monday to Saturday, 10 am to 8 pm. Sundays by appointment only."

Response

The saved reply was created.

id
string<uuid>
required

The saved reply's id.

Example:

"5e6f7a8b-9c0d-4e1f-a2b3-c4d5e6f7a8b9"

shortcut
string
required

What a teammate types after / to find it, without the slash.

Maximum string length: 40
Example:

"timings"

body
string
required

What the reply says.

Maximum string length: 2000
Example:

"We are open Monday to Saturday, 10 am to 8 pm. Sundays by appointment only."

createdAt
string<date-time>
required
Example:

"2026-10-01T06:30:00.000Z"

updatedAt
string<date-time>
required
Example:

"2026-10-04T11:12:45.920Z"