Package com.intercom.api.resources.tickets

Class AsyncTicketsClient

  • public class AsyncTicketsClient
extends java.lang.Object

    • Constructor Detail

      • AsyncTicketsClient

        public AsyncTicketsClient​(ClientOptions clientOptions)

    • Method Detail

      • withRawResponse

        public AsyncRawTicketsClient withRawResponse()
        Get responses with HTTP metadata like headers

      • reply

        public java.util.concurrent.CompletableFuture<TicketReply> reply​(ReplyToTicketRequest request)
        You can reply to a ticket with a message from an admin or on behalf of a contact, or with a note for admins.

      • reply

        public java.util.concurrent.CompletableFuture<TicketReply> reply​(ReplyToTicketRequest request,
                                                                 RequestOptions requestOptions)
        You can reply to a ticket with a message from an admin or on behalf of a contact, or with a note for admins.

      • create

        public java.util.concurrent.CompletableFuture<java.util.Optional<Ticket>> create​(CreateTicketRequest request)
        You can create a new ticket.

      • enqueueCreateTicket

        public java.util.concurrent.CompletableFuture<Jobs> enqueueCreateTicket​(EnqueueCreateTicketRequest request)
        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.

      • enqueueCreateTicket

        public java.util.concurrent.CompletableFuture<Jobs> enqueueCreateTicket​(EnqueueCreateTicketRequest request,
                                                                        RequestOptions requestOptions)
        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.

      • get

        public java.util.concurrent.CompletableFuture<java.util.Optional<Ticket>> get​(FindTicketRequest request)
        You can fetch the details of a single ticket.

      • get

        public java.util.concurrent.CompletableFuture<java.util.Optional<Ticket>> get​(FindTicketRequest request,
                                                                              RequestOptions requestOptions)
        You can fetch the details of a single ticket.

      • update

        public java.util.concurrent.CompletableFuture<java.util.Optional<Ticket>> update​(UpdateTicketRequest request)
        You can update a ticket.

      • search

        public java.util.concurrent.CompletableFuture<SyncPagingIterable<java.util.Optional<Ticket>>> search​(SearchRequest request)
        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 <= or >= 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 |

      • search

        public java.util.concurrent.CompletableFuture<SyncPagingIterable<java.util.Optional<Ticket>>> search​(SearchRequest request,
                                                                                                     RequestOptions requestOptions)
        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 <= or >= 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 |