Skip to main content
POST
/
tickets
Create a ticket
curl --request POST \
  --url https://{your-subdomain}.neetodesk.com/api/v1/public/tickets \
  --header 'Content-Type: application/json' \
  --header 'X-Api-Key: <x-api-key>' \
  --data '
{
  "email": "john@example.com",
  "subject": "How to resolve the pending payments",
  "description": "I need your help in resolving the pending payments.",
  "ticket_fields": {
    "Country": "USA"
  },
  "name": "John Luther",
  "channel": "email",
  "to": "[\"eve@example.com\",\"kevin@example.com\"]",
  "cc": "[\"eve@example.com\",\"kevin@example.com\"]",
  "group": "sales",
  "assignee_email": "oliver@example.com",
  "status": "open",
  "priority": "low",
  "category": "Questions",
  "sub_category_one": "Billing",
  "sub_category_two": "Refund",
  "tags": [
    "refund",
    "urgent"
  ],
  "resolution_due_date": "2025-12-31T23:59:59Z"
}
'
{
  "notice_code": "<string>",
  "ticket": {
    "id": "aaaabbbb-cccc-dddd-eeee-ffff00003333",
    "number": 42,
    "url": "https://example.neetodesk.com/admin/tickets/42"
  }
}
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.

Body

application/json
​
email
string
required

Email address of the customer.

Example:

"john@example.com"

​
subject
string
required

Subject for the ticket.

Example:

"How to resolve the pending payments"

​
description
string
required

Description for the ticket.

Example:

"I need your help in resolving the pending payments."

​
ticket_fields
object

Custom ticket fields. Refer to the ticket fields article for more details.

Example:
{ "Country": "USA" }
​
name
string

Name of the customer.

Example:

"John Luther"

​
channel
enum<string>

Source of the ticket. Defaults to api if not specified or if an invalid channel is provided.

Available options:
email,
ui,
twitter,
chat,
form,
api,
whatsapp,
telephony
Example:

"email"

​
to
string

Array of additional emails to be added to the to field of any responses from the ticket.

Example:

"[\"eve@example.com\",\"kevin@example.com\"]"

​
cc
string

Array of emails to be added to the cc field of any responses from the ticket.

Example:

"[\"eve@example.com\",\"kevin@example.com\"]"

​
group
string

Name of an existing group.

Example:

"sales"

​
assignee_email
string<email>

Email address belonging to a team member.

Example:

"oliver@example.com"

​
status
string

Status for the ticket. Default statuses include new, open, on_hold, waiting_on_customer, closed, spam, trash. Custom statuses are also supported.

Example:

"open"

​
priority
enum<string>

Priority for the ticket.

Available options:
low,
medium,
high,
urgent
Example:

"low"

​
category
string

Category for the ticket. Default categories include None, Questions, Incident, Problem, Feature request, Refund. Custom categories are also supported.

Example:

"Questions"

​
sub_category_one
string

Sub-category for the ticket.

Example:

"Billing"

​
sub_category_two
string

Second-level sub-category for the ticket.

Example:

"Refund"

​
tags
string[]

Tags to assign to the ticket.

Example:
["refund", "urgent"]
​
resolution_due_date
string<date-time>

Resolution due date for the ticket.

Example:

"2025-12-31T23:59:59Z"

Response

200 - application/json

OK - Request succeeded

​
notice_code
string
​
ticket
object