Skip to main content
POST
/
tickets
/
{ticket_id}
/
drafts
Create a draft comment for a ticket
curl --request POST \
  --url https://{your-subdomain}.neetodesk.com/api/v1/public/tickets/{ticket_id}/drafts \
  --header 'Content-Type: application/json' \
  --header 'X-Api-Key: <x-api-key>' \
  --data '
{
  "content": "We are looking into the issue.",
  "comment_type": "note",
  "author_email": "oliver@example.com"
}
'
{
  "id": "aaaabbbb-cccc-dddd-eeee-ffff00004444",
  "comment_type": "reply",
  "created_at": "2023-11-07T05:31:56Z",
  "updated_at": "2023-11-07T05:31:56Z",
  "content": "We are looking into the issue."
}
Deprecated: This is a v1 endpoint. It will continue to work, but we recommend migrating to the v2 equivalent for improved REST compliance (correct HTTP status codes, consistent response envelopes, and hyphenated URLs).
Replace {your-subdomain} with your workspace’s subdomain.
Learn how to find your subdomain in Identifying subdomain.

Headers

​
X-Api-Key
string
default:your-api-key
required

X-Api-Key is used to authenticate requests using an API key. Provide your API key in this header to access protected endpoints. Refer to Authentication for more information.

Path Parameters

​
ticket_id
string
required

ID of the ticket to retrieve comments for. You can use either the ticket ID (UUID) or ticket number (sequential number) interchangeably. Refer to Getting Ticket ID section for detailed instructions.

Body

application/json
​
content
string
required

Content for the draft comment. Cannot be blank.

Example:

"We are looking into the issue."

​
comment_type
enum<string>

Type of the comment. Defaults to reply.

Available options:
reply,
note
Example:

"note"

​
author_email
string

Optional email address of the person creating the draft. If provided, the signature stored in NeetoDesk for this user will be appended to the draft.

Example:

"oliver@example.com"

Response

200 - application/json

OK - Draft created successfully

​
id
string

Unique identifier for the draft

Example:

"aaaabbbb-cccc-dddd-eeee-ffff00004444"

​
comment_type
string

The type of the comment

Example:

"reply"

​
created_at
string<date-time>

Timestamp when the draft was created

​
updated_at
string<date-time>

Timestamp when the draft was last updated

​
content
string

Content of the draft comment

Example:

"We are looking into the issue."