Skip to content
nsin docs
EN فا

Reply to a ticket

POST
/tickets/{id}/messages
 
curl --request POST \
  --url https://api.nsin.ir/tickets/1/messages \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "message": "example" }'

Send JSON for a text-only reply, or multipart/form-data to attach files. See TicketAttachmentUpload for what may be attached.

With multipart/form-data, message may be empty as long as at least one file is attached; with JSON it is required. Replies are only accepted while the ticket is open.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
id
required
integer

Request Body required

Section titled “Request Body required ”
object
message
required
string
Example generated
{
  "message": "example"
}

Responses

Section titled “ Responses ”

200

Section titled “200 ”

The created message.

Media type application/json
object
id
integer
ticket_id
integer
author_user_id
integer
author

The message author.

object
key
additional properties
any
body
string
is_staff

True when written by support staff.

boolean
attachments
Array<object>
object
id
integer
message_id
integer
original_name
string
content_type
string
size_bytes
integer
url

Where to download the attachment.

string
created_at
string format: date-time
edited_at

When the message was last edited. Absent on a message that has never been edited — render the “edited” marker off this field, not off updated_at.

string format: date-time
edited_by_user_id

Who made the last edit. Absent on a message that has never been edited.

integer
edit_count

How many times the message has been edited. 0 for an untouched message.

integer
Example generated
{
  "id": 1,
  "ticket_id": 1,
  "author_user_id": 1,
  "author": {},
  "body": "example",
  "is_staff": true,
  "attachments": [
    {
      "id": 1,
      "message_id": 1,
      "original_name": "example",
      "content_type": "example",
      "size_bytes": 1,
      "url": "example"
    }
  ],
  "created_at": "2026-04-15T12:00:00Z",
  "edited_at": "2026-04-15T12:00:00Z",
  "edited_by_user_id": 1,
  "edit_count": 1
}

400

Section titled “400 ”

Invalid id, invalid body, an empty/oversized message, a closed ticket, or a rejected attachment — wrong type, over its size cap, more than eight files, or contents that do not match the extension.

Media type application/json

The single error shape used by every endpoint.

object
error
required

Human-readable description of what went wrong.

string
Examples
{
  "error": "ticket is closed"
}

401

Section titled “401 ”

Missing, malformed, revoked or expired API key. (A valid key whose account has been deactivated gets 403 account is inactive instead.)

Media type application/json

The single error shape used by every endpoint.

object
error
required

Human-readable description of what went wrong.

string
Examples
Example invalidKey 
{
  "error": "invalid API key"
}

403

Section titled “403 ”

The key is read-only and this endpoint is a write. Read-only keys may only issue GET, HEAD and OPTIONS.

Media type application/json

The single error shape used by every endpoint.

object
error
required

Human-readable description of what went wrong.

string
Examples
Example readOnly 
{
  "error": "read-only API key"
}

404

Section titled “404 ”

No such ticket on this account.

Media type application/json

The single error shape used by every endpoint.

object
error
required

Human-readable description of what went wrong.

string
Example 
{
  "error": "read-only API key"
}

429

Section titled “429 ”

The key exceeded its request budget (300 requests per minute by default).

Media type application/json

The single error shape used by every endpoint.

object
error
required

Human-readable description of what went wrong.

string
Examples
Example limited 
{
  "error": "rate limit exceeded"
}