corestack_ tickets_ list
List support tickets.
When to use it
List your company's support tickets, as the Tickets page lists them: open and waiting tickets by default, in the page's
order (pending first, then open and in progress by priority, then waiting, scheduled, on hold, resolved and closed;
newest first within each), 25 a page. Use it to find a ticket the person asks about, then read it with corestack_ticket_get.
Ask for it
Using the Corefinity MCP server, call corestack_tickets_list with status ["all_open_with_waiting"], priority ["emergency","high"], per_page 10. (List support tickets.) Tell me what it returned.Inputs
A client company your agency reaches; your own company when left out. At least 1.
Only tickets in this department. At least 1.
One environment, as before; it is added to enterprise_env_ids. At least 1.
Only tickets about any of these environments (ids from corestack_ticket_options_get's environments). Up to 50 items.
The page to read. At least 1.
Rows a page, 25 when left out. 1 to 100.
emergency, high, medium, low. Up to 4 items.
emergencyhighmediumlowOnly tickets for this person (a row's requester.id). At least 1.
all_open_with_waiting (the default: everything not resolved or closed), all_open (pending, open, in progress and on hold), all (every status), or statuses: pending, open, in_progress, waiting_on_customer, waiting_on_thirdparty, on_hold, scheduled, resolved, closed. Up to 20 items.
all_openall_open_with_waitingallpendingopenin_progressresolvedclosedwaiting_on_customerwaiting_on_thirdpartyon_holdscheduledOne website, as before; it is added to website_ids. At least 1.
Only tickets about any of these websites (ids from corestack_ticket_options_get). Up to 50 items.
Each row has id, subject, status and status_label, priority and priority_label, department, company,
websites and environments (every one the ticket names, id and name, by name), website and environment (the
first of each, or null), requester (id, name, email), scheduled_for (when a scheduled ticket comes back; null
once resolved or closed), created_at, updated_at and url (the ticket in the Control Panel). The answer also has
page, per_page, total and last_page.
Example call
{
"name": "corestack_tickets_list",
"arguments": {
"status": ["all_open_with_waiting"],
"priority": ["emergency", "high"],
"per_page": 10
}
}If it is refused
| Reason | What to do |
|---|---|
pin_refused | The token is limited to some sites. A ticket belongs to the whole company, so the step-up asks to let the token work everywhere in the company. |
tenant_mismatch | client_company_id is not a company your agency reaches. |
invalid_arguments | A status, priority, id or page value the list does not take, named in fields. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |