Working with Tickets in FreshDesk

Overview

The following operations allow you to work with tickets. Click an operation name to see details on how to use it.

For a sample proxy service that illustrates how to work with tickets, see Sample configuration.

Operation	Description
listTicketFields	Retrieves a list of tickets' fields.
deleteTicket	Deletes a particular ticket.
createTicket	Creates a new ticket in your help desk.
getTicket	Retrieves a particular ticket.
listTickets	Retrieves a list of tickets.
updateTicket	Updates a particular ticket.

Operation details

This section provides further details on the operations related to tickets.

Retrieves a list of tickets' fields.

The listTicketFields operation retrives a list of ticket's fields.

listTicketFields

<freshdesk.listTicketFields/>

Sample request

Following is a sample REST/JSON request that can be handled by the listTicketFields operation.

Sample Request for addNote

{
	"apiUrl":"https://wso2yasho.freshdesk.com",
	"apiKey":"SODsQllHr0NicsiRpRWw",
  	"apiVersion": "v2"
}

Deletes a particular ticket

ThedeleteTicketoperation deletes a particular ticket.

deleteTicket

<freshdesk.deleteTicket>
    <ticketId>{$ctx:ticketId}</ticketId>
</freshdesk.deleteTicket>

Properties

ticketId: Required - The unique identifier of the ticket specific to the account.

Sample request

Following is a sample REST/JSON request that can be handled by the deleteTicket operation.

Sample Request for deleteTicket

{
	"apiUrl":"https://wso2yasho.freshdesk.com",
	"apiKey":"SODsQllHr0NicsiRpRWw",
	"apiVersion": "v2",
	"ticketId":"38"
}

Creating a ticket

The createTicket operation creates a new ticket in your help desk.

createTicket

<freshdesk.createTicket>
    <requesterId>{$ctx:requesterId}</requesterId>
    <email>{$ctx:email}</email>
    <facebookId>{$ctx:facebookId}</facebookId>
    <phone>{$ctx:phone}</phone>
    <twitterId>{$ctx:twitterId}</twitterId>
    <name>{$ctx:name}</name>
    <subject>{$ctx:subject}</subject>
    <type>{$ctx:type}</type>
    <status>{$ctx:status}</status>
    <priority>{$ctx:priority}</priority>
    <customFields>{$ctx:customFields}</customFields>
    <description>{$ctx:description}</description>
    <responderId>{$ctx:responderId}</responderId>
    <ccEmails>{$ctx:ccEmails}</ccEmails>
    <dueBy>{$ctx:dueBy}</dueBy>
    <emailConfigId>{$ctx:emailConfigId}</emailConfigId>
    <frDueBy>{$ctx:frDueBy}</frDueBy>
    <groupId>{$ctx:groupId}</groupId>
    <productId>{$ctx:productId}</productId>
    <source>{$ctx:source}</source>
    <tags>{$ctx:tags}</tags>
</freshdesk.createTicket>

Properties

customFields: Pre-defined custom fields as a JSON Object.
status: The status of the ticket.
subject: The subject of the ticket.
emailConfigId: The ID of the email configuration that is used for this ticket.
requesterId: The ID of the requester. For existing contacts, requesterId can be passed instead of email.
groupId: The ID of the group to which the ticket is assigned.
source: The channel through which the ticket was created.
email: The email address of the requester. If no contact exists with this email address in FreshDesk, it will be added as a new contact.
type: The type of the particular ticket.
description: Plain text content of the ticket.
priority: The priority of the ticket.
ccEmails: The email address specified in the "cc" field of the incoming ticket email.
responderId: The ID of the agent to whom the ticket is assigned.
name: Name of the requester
facebookId: Facebook ID of the requester. If no contact exists with this facebook_id, then a new contact will be created.
phone: Phone number of the requester. If no contact exists with this phone number in Freshdesk, it will be added as a new contact. If the phone number is set and the email address is not, then the name attribute is mandatory.
twitterId: Twitter handle of the requester. If no contact exists with this handle in Freshdesk, it will be added as a new contact.
dueBy: Timestamp that denotes when the ticket is due to be resolved
productId: ID of the product to which the ticket is associated. It will be ignored if the email_config_id attribute is set in the request.
tags: Tags that have been associated with the ticket

Sample request

Following is a sample REST/JSON request that can be handled by the createTicketoperation.

Sample Request for createTicket

{
  "apiUrl": "https://wso2yasho.freshdesk.com",
  "apiKey": "SODsQllHr0NicsiRpRWw",
  "apiVersion": "v2",
  "requesterId": "19000247627",
  "email": "testTicket@gmail.com",
  "facebookId": "",
  "phone": "01112214567",
  "twitterId": "twitter",
  "name": "RequesterName",
  "description": "Creating Ticket",
  "subject": "testSubject",
  "emailConfigId": "",
  "frDueBy": "2016-10-03T12:15:00Z",
  "groupId": "19000023144",
  "productId": "19000000166",
  "source": "",
  "type": "issue",
  "responderId": "",
  "ccEmails": [
    "yyyt@gmail.com",
    "ttty@gmail.com"
  ],
  "customFields": {
    "z": "test"
  },
  "dueBy": "2016-10-03T12:15:00Z",
  "priority":1,
  "status": 2
}

Retrieving a ticket

The getTicket operation retrieves a particular ticket.

getTicket

<freshdesk.getTicket>
    <ticketId>{$ctx:ticketId}</ticketId>
</freshdesk.getTicket>

Properties

ticketId: Required - The unique identifier of the ticket specific to the account.

Sample request

Following is a sample REST/JSON request that can be handled by the getTicket operation.

Sample Request for getTicket

{
	"apiUrl": "https://wso2yasho.freshdesk.com",
    "apiKey": "SODsQllHr0NicsiRpRWw",
	"apiVersion": "v2",
	"ticketId":"1"
}

Retrieving a list of tickets

The listTickets operation retrieves a list of tickets.

listTickets

<freshdesk.listTickets>
    <predefinedFilters>{$ctx:predefinedFilters}</predefinedFilters>
    <requesterId>{$ctx:requesterId}</requesterId>
    <updatedSince>{$ctx:updatedSince}</updatedSince>
    <companyId>{$ctx:companyId}</companyId>
    <email>{$ctx:email}</email>
    <page>{$ctx:page}</page>
    <orderBy>{$ctx:orderBy}</orderBy>
    <orderType>{$ctx:orderType}</orderType>
    <include>{$ctx:include}</include>
</freshdesk.listTickets>

Properties

page: The requested page number.
email: The email address.
requesterId: The ID of the requester. For existing contacts, requesterId can be passed instead of email.
updatedSince: The ticket updated since a specific timestamp.
companyId: The unique identifier of the company.
predefinedFilters: The various filters available are new_and_my_open, watching, spam, deleted.
orderBy: Default sort order is created_at

include:When getting list of tickets, will get some specific details mentioned here.

orderType: Default sort order type is desc.

Sample request

Following is a sample REST/JSON request that can be handled by the listTickets operation.

Sample Request for listTickets

{
  "apiUrl": "https://wso2yasho.freshdesk.com",
  "apiKey": "SODsQllHr0NicsiRpRWw",
  "apiVersion": "v2",
  "predefinedFilters": "watching",
  "requesterId": "19000104481",
  "updatedSince": "",
  "companyId": "",
  "email": "test@gmail.com",
  "orderBy": "",
  "orderType": "desc",
  "include": "requester"
}

Updating a ticket

The updateTicket operation updates a particular ticket.

updateTicket

<freshdesk.updateTicket>
    <ticketId>{$ctx:ticketId}</ticketId>
    <requesterId>{$ctx:requesterId}</requesterId>
    <email>{$ctx:email}</email>
    <facebookId>{$ctx:facebookId}</facebookId>
    <phone>{$ctx:phone}</phone>
    <twitterId>{$ctx:twitterId}</twitterId>
    <name>{$ctx:name}</name>
    <subject>{$ctx:subject}</subject>
    <type>{$ctx:type}</type>
    <status>{$ctx:status}</status>
    <priority>{$ctx:priority}</priority>
    <customFields>{$ctx:customFields}</customFields>
    <description>{$ctx:description}</description>
    <responderId>{$ctx:responderId}</responderId>
    <ccEmails>{$ctx:ccEmails}</ccEmails>
    <dueBy>{$ctx:dueBy}</dueBy>
    <emailConfigId>{$ctx:emailConfigId}</emailConfigId>
    <frDueBy>{$ctx:frDueBy}</frDueBy>
    <groupId>{$ctx:groupId}</groupId>
    <productId>{$ctx:productId}</productId>
    <source>{$ctx:source}</source>
    <tags>{$ctx:tags}</tags>
</freshdesk.updateTicket>

Properties

customFields: Pre-defined custom fields as a JSON Object.
status: The status of the ticket.
ticketId: Required - The unique identifier of the ticket specific to the account.
subject: The subject of the ticket.
emailConfigId: The ID of the email configuration that is used for this ticket.
requesterId: The ID of the requester. For existing contacts, requesterId can be passed instead of email.
groupId: The ID of the group to which the ticket is assigned.
source: The channel through which the ticket was created.
email: The email address of the requester. If no contact exists with this email address in FreshDesk, it will be added as a new contact.
type: The type of the particular ticket.
description: Plain text content of the ticket.
priority: The priority of the ticket.
ccEmails: The email address specified in the "cc" field of the incoming ticket email.
responderId: The ID of the agent to whom the ticket is assigned.
name: Name of the requester
facebookId: Facebook ID of the requester. If no contact exists with this facebook_id, then a new contact will be created.
phone: Phone number of the requester. If no contact exists with this phone number in Freshdesk, it will be added as a new contact. If the phone number is set and the email address is not, then the name attribute is mandatory.
twitterId: Twitter handle of the requester. If no contact exists with this handle in Freshdesk, it will be added as a new contact.
dueBy: Timestamp that denotes when the ticket is due to be resolved
productId: ID of the product to which the ticket is associated. It will be ignored if the email_config_id attribute is set in the request.
tags: Tags that have been associated with the ticket

Note

When you use the updateTicket operation, you need to pass " " if you need to clear the value of any field.

Sample request

Following is a sample REST/JSON request that can be handled by the updateTicket operation.

Sample Request for updateTicket

{
  "apiUrl": "https://wso2yasho.freshdesk.com",
  "apiKey": "SODsQllHr0NicsiRpRWw",
  "apiVersion": "v2",
  "ticketId":"1",
  "requesterId": 19000247627,
  "email": "testTicket@gmail.com",
  "facebookId": "",
  "phone": "",
  "twitterId": "twitter",
  "name": "RequesterName",
  "description": "Creating Ticket",
  "subject": "testSubject",
  "emailConfigId": "",
  "frDueBy": "",
  "groupId": "",
  "productId": "",
  "source": "",
  "type": "issue",
  "responderId": "",
  "ccEmails": [
    "yyyt@gmail.com",
    "ttty@gmail.com"
  ],
  "customFields": {
    "z": "tttt"
  },
  "dueBy": "",
  "priority":1,
  "status": 2
}

Sample configuration

Following is a sample proxy service that illustrates how to connect to FreshDesk with the init operation and use the createTicket operation. The sample request for this proxy can be found in createTicket sample request. You can use this sample as a template for using other operations in this category.

Sample Proxy

<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="freshdesk_createTicket"
       transports="https,http"
       statistics="disable"
       trace="disable"
       startOnLoad="true">
   <target>
      <inSequence onError="faultHandlerSeq">
         <property expression="json-eval($.apiUrl)" name="apiUrl"/>
         <property expression="json-eval($.apiKey)" name="apiKey"/>
		 <property expression="json-eval($.apiVersion)" name="apiVersion"/>
		 <property expression="json-eval($.requesterId)" name="requesterId"/>
         <property expression="json-eval($.facebookId)" name="facebookId"/>
         <property expression="json-eval($.email)" name="email"/>
         <property expression="json-eval($.twitterId)" name="twitterId"/>
         <property expression="json-eval($.phone)" name="phone"/>
         <property expression="json-eval($.name)" name="name"/>
         <property expression="json-eval($.subject)" name="subject"/>
         <property expression="json-eval($.type)" name="type"/>
         <property expression="json-eval($.status)" name="status"/>
         <property expression="json-eval($.priority)" name="priority"/>
         <property expression="json-eval($.description)" name="description"/>
         <property expression="json-eval($.responderId)" name="responderId"/>
         <property expression="json-eval($.attachments)" name="attachments"/>
         <property expression="json-eval($.ccEmails)" name="ccEmails"/>
         <property expression="json-eval($.customFields)" name="customFields"/>
         <property expression="json-eval($.dueBy)" name="dueBy"/>
         <property expression="json-eval($.emailConfigId)" name="emailConfigId"/>
         <property expression="json-eval($.groupId)" name="groupId"/>
         <property expression="json-eval($.productId)" name="productId"/>
         <property expression="json-eval($.source)" name="source"/>
		 <property name="tags" expression="json-eval($.tags)"/> <freshdesk.init>
            <apiUrl>{$ctx:apiUrl}</apiUrl>
            <apiKey>{$ctx:apiKey}</apiKey>
			<apiVersion>{$ctx:apiVersion}</apiVersion>
		</freshdesk.init>
        <freshdesk.createTicket>
    		<requesterId>{$ctx:requesterId}</requesterId>
   			<email>{$ctx:email}</email>
    		<facebookId>{$ctx:facebookId}</facebookId>
    		<phone>{$ctx:phone}</phone>
    		<twitterId>{$ctx:twitterId}</twitterId>
    		<name>{$ctx:name}</name>
    		<subject>{$ctx:subject}</subject>
    		<type>{$ctx:type}</type>
    		<status>{$ctx:status}</status>
    		<priority>{$ctx:priority}</priority>
    		<customFields>{$ctx:customFields}</customFields>
    		<description>{$ctx:description}</description>
    		<responderId>{$ctx:responderId}</responderId>
    		<ccEmails>{$ctx:ccEmails}</ccEmails>
    		<dueBy>{$ctx:dueBy}</dueBy>
    		<emailConfigId>{$ctx:emailConfigId}</emailConfigId>
    		<frDueBy>{$ctx:frDueBy}</frDueBy>
    		<groupId>{$ctx:groupId}</groupId>
    		<productId>{$ctx:productId}</productId>
    		<source>{$ctx:source}</source>
    		<tags>{$ctx:tags}</tags>
		</freshdesk.createTicket>
         <respond/>
      </inSequence>
      <outSequence>
         <send/>
      </outSequence>
   </target>
   <description/>
</proxy>