corestack_ ticket_ create
Open a support ticket.
When to use it
Open a support ticket for Corefinity's support team, as the New Ticket form does. Ask the person what is wrong and which
websites it is about, then take the department, websites, environments and priority from corestack_ticket_options_get. The
ticket is raised as the form raises it: Corefinity's support team is told straight away and the person is emailed. Each
call opens a new ticket, so do not repeat it after a timeout without checking corestack_tickets_list first.
An emergency pages Corefinity's on-call engineers. Choose it only for a site that is down or losing orders, after telling
the person the emergency notice from corestack_ticket_options_get, and send confirm_emergency: true once they agree.
Ask for it
Using the Corefinity MCP server, call corestack_ticket_create with subject Checkout fails with a payment error, body Since 09:00 every order fails at the payment step with *Payment declined*., department_id 2, website_ids [7311,7312], enterprise_env_ids [20456], priority high. (Open a support ticket.) Tell me what it returned.Inputs
The problem in Markdown: what happens, since when, what was changed. Up to 65,535 characters.
The client company the ticket is for, when your agency raises it for a client; your own company when left out. At least 1.
true for an emergency, only after the person agreed.
One of the departments from corestack_ticket_options_get. At least 1.
One environment, as before; it is added to enterprise_env_ids. At least 1.
environments the options offer for the chosen websites. Up to 50 items.
low, medium (when left out), high or emergency.
emergencyhighmediumlowMarkdown steps to see the problem. Up to 65,535 characters.
One line saying what is wrong. Up to 255 characters.
One website, as before; it is added to website_ids. At least 1.
The websites the options offer that the problem affects. Up to 50 items.
Example call
{
"name": "corestack_ticket_create",
"arguments": {
"subject": "Checkout fails with a payment error",
"body": "Since 09:00 every order fails at the payment step with *Payment declined*.",
"department_id": 2,
"website_ids": [7311, 7312],
"enterprise_env_ids": [20456],
"priority": "high"
}
}If it is refused
| Reason | What to do |
|---|---|
confirm | An emergency without confirm_emergency: true. Tell the person what an emergency does, then ask. |
invalid_arguments | A field the form would not accept, named in fields (a department the form does not offer, or a company your agency does not reach). For websites and environments, in the form's own words: "That website is not one you can raise a ticket about." (a website of a company you cannot raise a ticket for), "That environment is not one you can choose for the chosen websites." (an environment of another website, or one the options do not list), and "Choose the website first: its environments depend on it." (environments without a website). |
tenant_mismatch | client_company_id is not a company you can raise a ticket for. |
pin_refused | The token is limited to some sites; a ticket belongs to the whole company. |
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. |