# Enqueue create ticket

Enqueues ticket creation for asynchronous processing, returning if the job was enqueued successfully to be processed. We attempt to perform a best-effort validation on inputs before tasks are enqueued. If the given parameters are incorrect, we won't enqueue the job.

Endpoint: POST /tickets/enqueue
Version: Unstable
Security: bearerAuth

## Header parameters:

  - `Intercom-Version` (string)
    Intercom API version.By default, it's equal to the version set in the app package.
    Enum: "1.0", "1.1", "1.2", "1.3", "1.4", "2.0", "2.1", "2.2", "2.3", "2.4", "2.5", "2.6", "2.7", "2.8", "2.9", "2.10", "2.11", "Unstable"

## Request fields (application/json):

  - `skip_notifications` (boolean)
    Option to disable notifications when a Ticket is created.
    Example: true

  - `ticket_type_id` (string, required)
    The ID of the type of ticket you want to create
    Example: "1234"

  - `contacts` (array, required)
    The list of contacts (users or leads) affected by this ticket. Currently only one is allowed
    Example: [{"id":"1234"}]

  - `conversation_to_link_id` (string)
    The ID of the conversation you want to link to the ticket. Here are the valid ways of linking two tickets:
 - conversation | back-office ticket
 - customer tickets | non-shared back-office ticket
 - conversation | tracker ticket
 - customer ticket | tracker ticket
    Example: "1234"

  - `company_id` (string)
    The ID of the company that the ticket is associated with. The unique identifier for the company which is given by Intercom
    Example: "5f4d3c1c-7b1b-4d7d-a97e-6095715c6632"

  - `created_at` (integer)
    The time the ticket was created. If not provided, the current time will be used.
    Example: 1590000000

  - `ticket_attributes` (object)
    The attributes set on the ticket. When setting the default title and description attributes, the attribute keys that should be used are  and . When setting ticket type attributes of the list attribute type, the key should be the attribute name and the value of the attribute should be the list item id, obtainable by [listing the ticket type](ref:get_ticket-types). For example, if the ticket type has an attribute called  of type , the key should be  and the value of the attribute should be the guid of the list item (e.g. ).
    Example: {"_default_title_":"Found a bug","_default_description_":"The button is not working"}

  - `assignment` (object)

  - `assignment.admin_assignee_id` (string)
    The ID of the admin to which the ticket is assigned. If not provided, the ticket will be unassigned.
    Example: "123"

  - `assignment.team_assignee_id` (string)
    The ID of the team to which the ticket is assigned. If not provided, the ticket will be unassigned.
    Example: "8"

## Response 200 fields (application/json):

  - `type` (string)
    The type of the object
    Enum: "job"

  - `id` (string, required)
    The id of the job that's currently being processed or has completed.
    Example: 20

  - `url` (string)
    API endpoint URL to check the job status.
    Example: "https://api.intercom.io/jobs/status/20"

  - `status` (string)
    The status of the job execution.
    Enum: "pending", "success", "failed"

  - `resource_type` (string)
    The type of resource created during job execution.
    Example: "ticket"

  - `resource_id` (string,null)
    The id of the resource created during job execution (e.g. ticket id)
    Example: 123

  - `resource_url` (string,null)
    The url of the resource created during job exeuction. Use this url to fetch the resource.
    Example: "http://api.intercom.io/tickets/123"

## Response 400 fields (application/json):

  - `type` (string, required)
    The type is error.list
    Example: "error.list"

  - `request_id` (string,null)
    Example: "f93ecfa8-d08a-4325-8694-89aeb89c8f85"

  - `errors` (array, required)
    An array of one or more error objects

  - `errors.code` (string, required)
    A string indicating the kind of error, used to further qualify the HTTP response code
    Example: "unauthorized"

  - `errors.message` (string,null)
    Optional. Human readable description of the error.
    Example: "Access Token Invalid"

  - `errors.field` (string,null)
    Optional. Used to identify a particular field or query parameter that was in error.
    Example: "email"

## Response 401 fields (application/json):

  - `type` (string, required)
    The type is error.list
    Example: "error.list"

  - `request_id` (string,null)
    Example: "f93ecfa8-d08a-4325-8694-89aeb89c8f85"

  - `errors` (array, required)
    An array of one or more error objects

  - `errors.code` (string, required)
    A string indicating the kind of error, used to further qualify the HTTP response code
    Example: "unauthorized"

  - `errors.message` (string,null)
    Optional. Human readable description of the error.
    Example: "Access Token Invalid"

  - `errors.field` (string,null)
    Optional. Used to identify a particular field or query parameter that was in error.
    Example: "email"