CorefinityCorefinityDocs
Open the Control PanelControl Panel
Support · 9 of 15

Update a ticket's priority

Changes the priority and answers the ticket as the list shows it; the change is emailed to everyone following the ticket, and sending the priority it already has changes nothing. Raising it to emergency pages Corefinity's on-call engineers instead, and is refused unless confirm_emergency is true.

PATCH/api/support/tickets/{ticket}/priority

Path parameters

ticketintegerRequired

The number of a ticket. Digits only. At least 1.

Body

confirm_emergencyboolean

true for emergency, once you agree to what the emergency_notice of the ticket choices says.

prioritystringRequired
emergencyhighmediumlow

Returns

200 The ticket with its new priority.

Fields of the 200 answer
companyobject or any or nullRequired

The company the ticket is for.

created_atstring or nullRequired

Format: date-time.

departmentobject or any or nullRequired

The department the ticket is in.

environmentobject or any or nullRequired

The first of environments, or null.

environmentsarray of objectsRequired

Every environment the ticket is about.

Fields of each item
idintegerRequired

At least 1.

namestringRequired
idintegerRequired

At least 1.

prioritystringRequired
emergencyhighmediumlow
priority_labelstringRequired
requesterobject or any or nullRequired

Who the ticket is for.

scheduled_forstring or nullRequired

When a scheduled ticket comes back to Corefinity's queue. Null once a ticket is resolved or closed. Format: date-time.

statusstringRequired
pendingopenin_progresswaiting_on_customerwaiting_on_thirdpartyon_holdscheduledresolvedclosed
status_labelstringRequired
subjectstringRequired
updated_atstring or nullRequired

Format: date-time.

urlstringRequired

The ticket in the Control Panel.

websiteobject or any or nullRequired

The first of websites, or null.

websitesarray of objectsRequired

Every website the ticket is about.

Fields of each item
idintegerRequired

At least 1.

namestringRequired

If it is refused

StatusReasonWhat to do
401noneSend a valid token as Authorization: Bearer <token>.
403scope_requiredUse a token with the scope named in scope.
404noneCheck the id. You see only what your account can reach.
422confirmThe action needs an explicit confirmation field. Ask the person, then send it.
422invalidFix the field named in field; errors says why.
429rate_limitedWait for the seconds in Retry-After.

Reasons are listed by name in Errors and refusals.

The same task elsewhere

curl -X PATCH https://manage.corefinity.com/api/support/tickets/48210/priority \
  -H "Authorization: Bearer $COREFINITY_TOKEN" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "priority": "low"
  }'
{
  "company": {
    "id": 1204,
    "name": "Harbour & Finch"
  },
  "created_at": "2026-11-02T08:14:03Z",
  "department": {
    "id": 21,
    "name": "Support"
  },
  "environment": {
    "id": 1311,
    "name": "Production"
  },
  "environments": [
    {
      "id": 1311,
      "name": "Production"
    }
  ],
  "id": 48210,
  "priority": "low",
  "priority_label": "Low",
  "requester": {
    "email": "[email protected]",
    "id": 2041,
    "name": "Eleanor Finch"
  },
  "scheduled_for": null,
  "status": "waiting_on_customer",
  "status_label": "Waiting on customer",
  "subject": "Checkout returns a 502",
  "updated_at": "2026-11-03T16:40:11Z",
  "url": "https://manage.corefinity.com/resources/tickets/48210",
  "website": {
    "id": 1310,
    "name": "Harbour & Finch trade"
  },
  "websites": [
    {
      "id": 1310,
      "name": "Harbour & Finch trade"
    }
  ]
}
Try it

Try it is off for this endpointIt sends email to real people. Copy the request and run it yourself when you are sure.

Was this helpful?
Open in ClaudeOpen in ChatGPT