Skip to main content
POST
Reply to an existing message thread

Authorizations

session_id
string
header
required

Legacy session-id header retained for backwards compatibility with older first-party clients. New integrations should prefer bearerAuth or apiKeyAuth.

Path Parameters

client_id
integer<int64>
required
Example:

207

session_id
string
required
message_id
integer<int64>
required

Root message id of the thread being replied to.

Example:

8801

Body

application/json
message
string
required

Reply body. Validator rule: required|string|max:20000.

Example:

"Thanks for asking! ..."

fileName
string | null

Validator rule: nullable|string|max:255.

fileStorageKey
string | null

S3 storage key from the recipient-portal upload endpoint. Validator rule: nullable|string|max:255.

Response

Reply created.

status
string
Example:

"success"

message
object