List support tickets
Answers the tickets you can see (your company's, those of the companies your agency looks after and any you follow) in the order of the Tickets page of the Control Panel: new tickets first, then open and in-progress ones by priority, then the rest, newest first within each. Paged by page number: page and per_page.
Query parameters
all_open_with_waiting (the default: every ticket that is not resolved or closed), all_open (new, open, in progress and on hold), all, or one or more statuses, comma-separated: pending, open, in_progress, waiting_on_customer, waiting_on_thirdparty, on_hold, scheduled, resolved, closed.
One or more of emergency, high, medium and low, comma-separated.
One company's tickets, for an agency with more than one company. At least 1.
Tickets about any of these websites: up to 50 ids, comma-separated.
Tickets about one website. At least 1.
Tickets about any of these environments: up to 50 ids, comma-separated.
Tickets about one environment. At least 1.
Tickets for that person. At least 1.
Tickets in that department. At least 1.
The page to read, starting at 1. Defaults to 1.
Items a page. Each endpoint names the sizes it accepts. Defaults to 25. 1 to 100.
Returns
200 One page of tickets.
Fields of the 200 answer
Fields of each item
The company the ticket is for.
Format: date-time.
The department the ticket is in.
The first of environments, or null.
Every environment the ticket is about.
Fields of each item
At least 1.
At least 1.
emergencyhighmediumlowWho the ticket is for.
When a scheduled ticket comes back to Corefinity's queue. Null once a ticket is resolved or closed. Format: date-time.
pendingopenin_progresswaiting_on_customerwaiting_on_thirdpartyon_holdscheduledresolvedclosedFormat: date-time.
The ticket in the Control Panel.
The first of websites, or null.
Every website the ticket is about.
Fields of each item
At least 1.
If it is refused
| Status | Reason | What to do |
|---|---|---|
401 | none | Send a valid token as Authorization: Bearer <token>. |
403 | scope_required | Use a token with the scope named in scope. |
422 | invalid | Fix the field named in field; errors says why. |
429 | rate_limited | Wait for the seconds in Retry-After. |
Reasons are listed by name in Errors and refusals.
The same task elsewhere
curl https://manage.corefinity.com/api/support/tickets \
-H "Authorization: Bearer $COREFINITY_TOKEN" \
-H "Accept: application/json"use Illuminate\Support\Facades\Http;
$response = Http::withToken(env('COREFINITY_TOKEN'))
->acceptJson()
->get('https://manage.corefinity.com/api/support/tickets');
$data = $response->json();const res = await fetch('https://manage.corefinity.com/api/support/tickets', {
method: 'GET',
headers: {
Authorization: `Bearer ${process.env.COREFINITY_TOKEN}`,
Accept: 'application/json',
},
});
// An answer with no body (204) has nothing to parse.
const text = await res.text();
const data = text && JSON.parse(text);import os
import requests
res = requests.get(
"https://manage.corefinity.com/api/support/tickets",
headers={
"Authorization": f"Bearer {os.environ['COREFINITY_TOKEN']}",
"Accept": "application/json",
},
)
data = res.json() if res.content else None{
"last_page": 1,
"page": 1,
"per_page": 25,
"tickets": [
{
"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": "high",
"priority_label": "High",
"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"
}
]
}
],
"total": 1
}{
"message": "Unauthenticated."
}{
"code": "scope_required",
"message": "This access token does not have the destructive scope this needs. Use a token with the destructive scope.",
"reason": "scope_required",
"scope": "destructive"
}{
"code": "invalid",
"errors": {
"per_page": [
"The per page may not be greater than 100."
]
},
"field": "per_page",
"message": "The per page may not be greater than 100.",
"reason": "invalid"
}{
"code": "rate_limited",
"message": "Too many requests. Try again in 60 seconds.",
"reason": "rate_limited",
"retry_after_seconds": 60
}