Skip to main content
POST
Create or update a ticket

Authorizations

Authorization
string
header
required

Partner API key (e.g. nerds_live_a8f3d9k2m5n7p1q4r6t8v0w2x4y6z8)

Path Parameters

id
string
required

Ticket ID from the source system (e.g., Zendesk ticket ID)

Example:

"328099"

Body

application/json

Fields for creating or updating a ticket. All fields are optional on update — only provided fields are changed.

organization_id
string | null

Organization ID as defined in the source system and synced via POST /organization/{id}

Example:

"ORG-5001"

contact_id
string | null

Contact ID as defined in the source system and synced via POST /contact/{id}

Example:

"C-10042"

group_id
string | null

Group ID as defined in the source system and synced via POST /reference/group

Example:

"GRP-100"

agent_id
string | null

Agent ID as defined in the source system and synced via POST /reference/agent

Example:

"AGT-42"

title
string | null

Ticket subject/title

Example:

"Internet connection issue"

status
string | null

Status id as defined in the source system and synced via POST /reference/status

Example:

"open"

priority
string | null

Priority id as defined in the source system and synced via POST /reference/priority

Example:

"high"

type
string | null

Type id as defined in the source system and synced via POST /reference/type

Example:

"support"

category
string | null

Category id as defined in the source system and synced via POST /reference/category

Example:

"technical"

subcategory
string | null

Subcategory id as defined in the source system and synced via POST /reference/subcategory

Example:

"connectivity"

created_at
string<date-time> | null

Original creation timestamp (from source system)

Example:

"2026-03-09T10:30:00Z"

updated_at
string<date-time> | null

Last update timestamp (from source system)

Example:

"2026-03-09T14:15:00Z"

Response

Ticket updated

success
boolean
Example:

true

data
object
message
string