---
title: "corestack_ticket_create"
url: https://docs.corefinity.com/mcp/tools/corestack_ticket_create
type: tool
last_updated: 2026-11-13
feature: support
related:
  - https://docs.corefinity.com/guides/support/raise-and-follow-a-ticket.md
---
# corestack_ticket_create

**Open a support ticket.** Open a support ticket for Corefinity, as the New Ticket form does. Take the department, websites and environments from corestack_ticket_options_get. body is Markdown. An emergency priority pages on-call engineers: confirm_emergency must be true, after the person agreed. Scope: write.

- Scope: `write`
- Runs as a task: no

## 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.

## Inputs

- `subject` (string, 1–255, required): one line saying what is wrong.
- `body` (string, required): the problem in Markdown: what happens, since when, what was changed.
- `department_id` (integer, required): one of the `departments` from corestack_ticket_options_get.
- `priority` (string, optional): `low`, `medium` (when left out), `high` or `emergency`.
- `website_ids` (array of integers, optional, up to 50): the `websites` the options offer that the problem affects.
- `website_id` (integer, optional): one website, as before; it is added to `website_ids`.
- `enterprise_env_ids` (array of integers, optional, up to 50): `environments` the options offer for the chosen websites.
- `enterprise_env_id` (integer, optional): one environment, as before; it is added to `enterprise_env_ids`.
- `replication_step` (string, optional): Markdown steps to see the problem.
- `confirm_emergency` (boolean, optional): `true` for an emergency, only after the person agreed.
- `client_company_id` (integer, optional): the client company the ticket is for, when your agency raises it for a client;
  your own company when left out.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "body": {
      "maxLength": 65535,
      "minLength": 1,
      "type": "string"
    },
    "client_company_id": {
      "minimum": 1,
      "type": "integer"
    },
    "confirm_emergency": {
      "type": "boolean"
    },
    "department_id": {
      "minimum": 1,
      "type": "integer"
    },
    "enterprise_env_id": {
      "minimum": 1,
      "type": "integer"
    },
    "enterprise_env_ids": {
      "items": {
        "minimum": 1,
        "type": "integer"
      },
      "maxItems": 50,
      "type": "array"
    },
    "priority": {
      "enum": [
        "emergency",
        "high",
        "medium",
        "low"
      ],
      "type": "string"
    },
    "replication_step": {
      "maxLength": 65535,
      "type": "string"
    },
    "subject": {
      "maxLength": 255,
      "minLength": 1,
      "type": "string"
    },
    "website_id": {
      "minimum": 1,
      "type": "integer"
    },
    "website_ids": {
      "items": {
        "minimum": 1,
        "type": "integer"
      },
      "maxItems": 50,
      "type": "array"
    }
  },
  "required": [
    "subject",
    "body",
    "department_id"
  ],
  "type": "object"
}
```

## Refusals

- `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.
- The refusals every tool can answer: `invalid_arguments`, `scope_required`, `rate_limited`, `temporarily_unavailable`,
  `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "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"
  }
}
```

## Prompt

```text
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.
```

## The same task elsewhere

- Guide: [Support tickets](https://docs.corefinity.com/guides/support/raise-and-follow-a-ticket.md)
