Update an administration ticket status and reply

Change ticket status or the administrator reply. Does not create a reward approval or external Issue.

PATCH https://api.moi.matrixorigin.cn/v5/admin/feedback-tickets/{id}

Before you call this API

Prepare a Genesis administrator Bearer token valid for the current environment. An ordinary personal access token, X-API-Key, or Workspace Owner status is insufficient. Session-authenticated writes also require CSRF protection. See AI Studio. Replace example IDs with real tickets you are authorized to view.

{}, null, or two null fields do not satisfy the update requirement. Only the target state is currently validated; transitions are not guaranteed to follow one sequence, and processing and closed may be reset between each other. Update responses do not project identity directory data, so user_info is not guaranteed to match details.

Request parameters

curl -X PATCH "https://api.moi.matrixorigin.cn/v5/admin/feedback-tickets/ticket-example" \
  -H "Authorization: Bearer $GENESIS_ADMIN_TOKEN" \
  -H "Content-Type: application/json" \
  --data '{"status":"processing","admin_reply":""}'

Parameter

Type

Required

Description

Authorization

string

Yes for the Bearer example

Bearer followed by a trusted administrator token for this environment. Do not also set an API Key.

id

string

Yes

Ticket ID in the path.

status

string

At least one of this and admin_reply

Only processing or closed is allowed; submitted cannot be written. Omission/null preserves the previous value.

admin_reply

string / null

At least one of this and status

Omission/null preserves the previous value; an explicit empty string clears it to a string.

Successful response

{
  "code": 0,
  "data": {
    "id": "ticket-example",
    "ticket_no": "FB-EXAMPLE",
    "account_id": "principal-example",
    "uc_account_id": "uc-example",
    "title": "示例反馈",
    "description": "界面显示结果与预期不同。",
    "expected_behavior": null,
    "actual_behavior": null,
    "reproduction_steps": null,
    "suggested_priority": null,
    "status": "processing",
    "admin_reply": "",
    "created_at": "2026-11-12T04:00:00Z",
    "updated_at": "2026-11-12T04:00:00Z",
    "messages": [
      {
        "sequence": 0,
        "role": "user",
        "content": "示例反馈内容。",
        "created_at": "2026-11-12T04:00:00Z"
      }
    ]
  }
}

Field

Type

Description

code

integer

Numeric 0 on success.

data

object

Updated ticket.

data.id

string

Object ID.

data.ticket_no

string / null

Feedback number; may be null.

data.account_id

string

Product principal ID that submitted the ticket.

data.uc_account_id

string / null

UC account facts saved at creation; may be null. This is not the current administrator’s account.

data.user_info

object / null, optional

Submitter information projected from the current identity directory for administrator reads. Optional; not persisted in the ticket.

data.title

string / null

Title; may be null on a ticket.

data.description

string / null

Problem description; may be null.

data.expected_behavior

string / null

Expected behavior; may be null.

data.actual_behavior

string / null

Actual behavior; may be null.

data.reproduction_steps

string / null

Reproduction steps; may be null.

data.suggested_priority

string / null

User-suggested priority; may be null and does not establish triage.

data.status

string

Ticket state: submitted, processing, or closed.

data.admin_reply

string / null

Administrator reply; may be null. An empty string differs from null.

data.created_at

string

Creation time in RFC 3339.

data.updated_at

string

Update time in RFC 3339.

data.messages

object (array of objects), optional

Optional conversation records. Not loaded for lists; an empty collection in details may be omitted because of omitempty.

data.github_issue

object / null, optional

Optional primary GitHub Issue request. Lists, details, and updates may all include this association.

data.reward_event

object / null, optional

Optional reward approval facts. Not currently loaded for lists; returned by details and updates when present.

See Shared objects for all public fields of nested tickets, users, messages, approval facts, and GitHub requests. Nullability and omission are documented separately; the old SDK fixture’s submitter_email is not a current field.

Error responses

{"code":"Unauthorized","msg":"Unauthorized"}

Field

Type

Description

code

string / integer

Varies by failure stage; the example uses an authentication-layer string.

msg

string

Authentication or service-layer failure text; service text is usually localized.

message

string

Text for a numeric parameter-parsing error code; distinct from msg.

data

null

Current service-layer responseEnvelope errors retain null; authentication examples may omit this field.

details

object

Text-field 422 errors may include field/reason and other details; see the error descriptions.

HTTP / code

Conditions and handling

401 / Unauthorized

Rejected by authentication. Do not use an ordinary PAT or also supply X-API-Key.

403 / ErrForbidden

Trusted administrator eligibility was not obtained, or the current caller identity does not match it.

404 / ErrFeedbackTicketNotFound

The target ticket does not exist. Current service errors return code/msg/data:null.

503 / ErrServiceUnavailable

Classified identity, directory, or authorization dependency unavailability, or network timeout.

500 / ErrServer

Internal processing or localization failure. Read back after a write error to confirm the result.

400 / code:2

Request decoding failure; uses numeric code and message.

400 / ErrParamInvalid or ErrFeedbackTicketStatusInvalid

Missing actual update fields or invalid target status.

See Errors and recovery for all error families and stages.

Last updated on