# Tickets Everything about your tickets ## Add tag to a ticket - [POST /tickets/{ticket_id}/tags](https://developers.intercom.com/docs/references/2.14/rest-api/api.intercom.io/tags/attachtagtoticket.md): You can tag a specific ticket. This will return a tag object for the tag that was added to the ticket. ## Remove tag from a ticket - [DELETE /tickets/{ticket_id}/tags/{id}](https://developers.intercom.com/docs/references/2.14/rest-api/api.intercom.io/tags/detachtagfromticket.md): You can remove tag from a specific ticket. This will return a tag object for the tag that was removed from the ticket. ## Reply to a ticket - [POST /tickets/{id}/reply](https://developers.intercom.com/docs/references/2.14/rest-api/api.intercom.io/tickets/replyticket.md): You can reply to a ticket with a message from an admin or on behalf of a contact, or with a note for admins. ## Add tag to a ticket - [POST /tickets/{ticket_id}/tags](https://developers.intercom.com/docs/references/2.14/rest-api/api.intercom.io/tickets/attachtagtoticket.md): You can tag a specific ticket. This will return a tag object for the tag that was added to the ticket. ## Remove tag from a ticket - [DELETE /tickets/{ticket_id}/tags/{id}](https://developers.intercom.com/docs/references/2.14/rest-api/api.intercom.io/tickets/detachtagfromticket.md): You can remove tag from a specific ticket. This will return a tag object for the tag that was removed from the ticket. ## Create a ticket - [POST /tickets](https://developers.intercom.com/docs/references/2.14/rest-api/api.intercom.io/tickets/createticket.md): You can create a new ticket. ## Enqueue create ticket - [POST /tickets/enqueue](https://developers.intercom.com/docs/references/2.14/rest-api/api.intercom.io/tickets/enqueuecreateticket.md): 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. ## Update a ticket - [PUT /tickets/{id}](https://developers.intercom.com/docs/references/2.14/rest-api/api.intercom.io/tickets/updateticket.md): You can update a ticket. ## Retrieve a ticket - [GET /tickets/{id}](https://developers.intercom.com/docs/references/2.14/rest-api/api.intercom.io/tickets/getticket.md): You can fetch the details of a single ticket. ## Delete a ticket - [DELETE /tickets/{id}](https://developers.intercom.com/docs/references/2.14/rest-api/api.intercom.io/tickets/deleteticket.md): You can delete a ticket using the Intercom provided ID. ## Search tickets - [POST /tickets/search](https://developers.intercom.com/docs/references/2.14/rest-api/api.intercom.io/tickets/searchtickets.md): You can search for multiple tickets by the value of their attributes in order to fetch exactly which ones you want. To search for tickets, you send a POST request to https://api.intercom.io/tickets/search. This will accept a query object in the body which will define your filters. {% admonition type="warning" name="Optimizing search queries" %} Search queries can be complex, so optimizing them can help the performance of your search. Use the AND and OR operators to combine multiple filters to get the exact results you need and utilize pagination to limit the number of results returned. The default is 20 results per page. See the pagination section for more details on how to use the starting_after param. {% /admonition %} ### Nesting & Limitations You can nest these filters in order to get even more granular insights that pinpoint exactly what you need. Example: (1 OR 2) AND (3 OR 4). There are some limitations to the amount of multiples there can be: - There's a limit of max 2 nested filters - There's a limit of max 15 filters for each AND or OR group ### Accepted Fields Most keys listed as part of the Ticket model are searchable, whether writeable or not. The value you search for has to match the accepted type, otherwise the query will fail (ie. as created_at accepts a date, the value cannot be a string such as "foobar"). The source.body field is unique as the search will not be performed against the entire value, but instead against every element of the value separately. For example, when searching for a conversation with a "I need support" body - the query should contain a = operator with the value "support" for such conversation to be returned. A query with a = operator and a "need support" value will not yield a result. | Field | Type | | :---------------------------------------- | :--------------------------------------------------------------------------------------- | | id | String | | created_at | Date (UNIX timestamp) | | updated_at | Date (UNIX timestamp) | | title | String | | description | String | | category | String | | ticket_type_id | String | | contact_ids | String | | teammate_ids | String | | admin_assignee_id | String | | team_assignee_id | String | | open | Boolean | | state | String | | snoozed_until | Date (UNIX timestamp) | | ticket_attribute.{id} | String or Boolean or Date (UNIX timestamp) or Float or Integer | {% admonition type="info" name="Searching by Category" %} When searching for tickets by the category field, specific terms must be used instead of the category names: * For Customer category tickets, use the term request. * For Back-office category tickets, use the term task. * For Tracker category tickets, use the term tracker. {% /admonition %} ### Accepted Operators {% admonition type="info" name="Searching based on created_at" %} You may use the = operators to search by created_at. {% /admonition %} The table below shows the operators you can use to define how you want to search for the value. The operator should be put in as a string ("="). The operator has to be compatible with the field's type (eg. you cannot search with > for a given string value as it's only compatible for integer's and dates). | Operator | Valid Types | Description | | :------- | :----------------------------- | :----------------------------------------------------------- | | = | All | Equals | | != | All | Doesn't Equal | | IN | All | In Shortcut for OR queries Values most be in Array | | NIN | All | Not In Shortcut for OR ! queries Values must be in Array | | > | Integer Date (UNIX Timestamp) | Greater (or equal) than | | < | Integer Date (UNIX Timestamp) | Lower (or equal) than | | ~ | String | Contains | | !~ | String | Doesn't Contain | | ^ | String | Starts With | | $ | String | Ends With |