Skip to main content
POST
Create Ticket Message

Authentication and permissions

Token requirements: User-based token (OAuth) or Organization-scoped API key or Team-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Team keys must allow every team checked by the request. OAuth access depends on the user’s roles and resource access.
  • Requester reply: The caller must be authorized for the ticket requester and post as themselves. Not available for internal notes, or for team-private tickets while team-only ticket access is enforced.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

ticket_id
string
required

The ID of the ticket to add a message to.

Body

application/json
message
string

The content of the message.

authorUserId
string

The ID of the user who authored the message.

triggerHelpAgent
boolean | null

Optional. Whether to trigger the AI help agent workflow for this message. Defaults to true. Set to false to suppress the help agent (e.g. when syncing messages from an external system or posting automated replies).

isInternalNote
boolean | null

Optional. When true, the message is created as an internal note, visible only to team members and never surfaced to the requester. Defaults to false.

createdAt
string<date-time> | null

A timestamp in RFC 3339 format (e.g., "2025-01-15T01:30:15Z").

Example:

"2025-01-15T01:30:15.000Z"

Response

200 - application/json

Success

data
data · object