Introduction
The Freshservice API
Freshservice is a cloud-based IT Service Management solution that was designed using ITIL best practices. Freshservice helps IT organizations streamline their service delivery processes with a strong focus on user experience and employee happiness.
Freshservice's APIs belong to the Representational State Transfer (REST) category. They allow you to perform 'RESTful' operations such as reading, modifying, adding or deleting data from your service desk. The APIs also support Cross-Origin Resource Sharing (CORS).
Note: This documentation is for the v2.0 of the APIs. Documentation for the v1.0 APIs can be found here.
What API commands are used by Freshservice?
Freshservice APIs are plain JSON over HTTP and use the following HTTP verbs:
Command | Purpose |
---|---|
POST | Create an object |
GET | Fetch one or more objects |
PUT | Update an object / Restore an object |
DELETE | Remove an object |
Note: All API requests should hit the secured endpoint i.e. only HTTPS
What's New?
Version 2 of the API brings several new features as well as changes to the previous APIs. This section highlights some of the new features introduced in v2.
- Higher rate limits as a result of significant performance enhancements
- Improved error handling - errors will return appropriate HTTP status codes and an error body
- New APIs that enable you to Reply to a ticket and enhancements to existing APIs that enable you to Update a ticket's description, Update a ticket's notes, and Retrieve a list of tickets that have been recently modified
- Only JSON is supported in V2
- Only SSL calls (HTTPS) will be allowed
- Works only via Freshservice domains and not via custom CNAMEs
- Support for page sizes up to 100 has been added
Rate limit
Freshservice accounts created on or after 01-Sep-2020 will use minute-level rate limiting. The limits vary based on the Freshservice plan. Certain API operations also have sublimits within the overall limit. This limit is applied on an account wide basis irrespective of factors such as the number of agents or IP addresses used to make the calls.
Action | Rate Limit/Min | |||
---|---|---|---|---|
Starter | Growth | Pro | Enterprise | |
Overall Limit | 100 | 200 | 400 | 500 |
Sub Limits | ||||
List All Tickets | 40 | 70 | 120 | 140 |
View Ticket | 50 | 80 | 140 | 160 |
Create Ticket | 50 | 80 | 140 | 160 |
Update Ticket | 50 | 80 | 140 | 160 |
List All Assets | 40 | 70 | 120 | 140 |
Update Asset | 50 | 80 | 140 | 160 |
List All Agents | 40 | 70 | 120 | 140 |
List All Requesters | 40 | 70 | 120 | 140 |
Note:
1. Please follow the best practices to stay under the rate limit.
2. If you need more than the default limit, please contact us.
3. Even invalid requests will count towards the rate limit.
4. Embedding additional resources will consume 1 credit if performed from a SHOW action, and 3 credits if performed from a LIST action.
5. Some custom apps (freshplugs) consume API calls which also count towards the rate limit.
You can check your current rate limit status by looking at the following HTTP headers which are returned in response to every API request.
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
X-Ratelimit-Total: 3000
X-Ratelimit-Remaining: 998
X-Ratelimit-Used-CurrentRequest: 1
X-Freshservice-Api-Version: latest=v2; requested=v2
Header Name | Description |
---|---|
X-RateLimit-Total | Total number of API calls allowed per hour. |
X-RateLimit-Remaining | The number of requests remaining in the current rate limit window. |
X-RateLimit-Used-CurrentRequest | The number of API calls consumed by the current request. Most API requests consume one call, however, including additional information in the response will consume more calls. |
Retry-After | The number in seconds that you will have to wait to fire your next API request. This header will be returned only when the rate limit has been reached. |
If your API request is received after the rate limit has been reached, Freshservice will return an error in the response. The Retry-After value in the response header will tell you how long you need to wait before you can send another API request.
HTTP/1.1 429
Content-Type: application/json; charset=utf-8
Retry-After: 1521
Policies
Freshservice APIs are classified into either production or beta APIs. A production API is one that has been made available for public use and is stable. A beta API is one that is still in development or is for internal or limited use and whose stability cannot be guaranteed. Beta APIs may be removed or modified at any time without advance notice. Please note that the following policies apply to production APIs only.
Deprecation Policy
The scope of the V2 API is currently limited to only tickets and conversations. Once all modules are made available through the API, API V1 would be deprecated after a given notice period.
Breaking Change Policy
Changes that do not break an API, such as adding a new attribute can be made at any time. Changes that break a production level API such as removing attributes or making major changes to the API’s behavior will only be done with an advance notice of 60 days. However, there may be rare occasions where due to legal, performance, or security reasons, we are forced to make breaking changes without advance notice.
Changelog
- Freshservice APIs support Oauth authentication. Refer scopes required against the respective APIs.
- 'Create a Child Ticket' API allows creating incidents as child tickets for SR/Case/Query/Issue/Request apart from an incident.
- 'Create a Child Service Request' API allows creating SR/Case/Query/Issue/Request as child ticket for an Incident/Major Incident also.
- List All Groups will return agent groups only from the specified workspace, or the primary workspace if workspace_id is not specified.
- Restricted groups are supported in all workspaces
- Audit logs of requesters ("type": ["requester"]) can be exported
- Audit logs of a requester ("requester_id": number) can be exported
Following attributes are no longer supported:
In the object "Agent"
- Attribute ticket_scope is no longer supported. Instead use roles -> assignment_scope
- Attribute problem_scope is no longer supported. Instead use roles -> assignment_scope
- Attribute change_scope is no longer supported. Instead use roles -> assignment_scope
- Attribute release_scope is no longer supported. Instead use roles -> assignment_scope
- Attribute scopes is no longer supported. Instead use roles -> assignment_scope
- Attribute group_ids is no longer supported. Instead use member_of and observer_of
- Attribute role_ids is no longer supported. Instead use roles -> role_id
In the object "group"
- Attribute agent_ids is no longer supported. Instead use members and observers
- Username and password-based basic authentication of Freshservice APIs is no longer supported. Instead use basic auth with API Key authentication.
- Initial version - V2 APIs for tickets and conversations
Authentication
How does it work? Who can access my helpdesk? Can everybody see my data?
Before you can set the priority of a ticket or change a customer's name or use any of the APIs listed above, you need to "authenticate your ID" or "log in" in the same way you log in to your helpdesk's web portal.
You can use your personal API key to authenticate the request. If you use the API key, there is no need for a password. You can use any set of characters as a dummy password.
curl -v -u apikey:X -H "Content-Type: application/json" -X GET 'https://domain.freshservice.com/api/v2/tickets'
For example, if your API key is abcdefghij1234567890, the curl command to use is:
curl -v -u abcdefghij1234567890:X -H "Content-Type: application/json" -X GET 'https://domain.freshservice.com/api/v2/tickets'
Where can I find my API key?
- Login to your Support Portal
- Click on your profile picture on the top right corner of your portal
- Go to Profile settings Page
- Your API key will be available below the change password section to your right
Freshservice supports Basic Access Authorization only with API key.
curl -v -u api_key:X -H "Content-Type: application/json" -X 'GET https://domain.freshservice.com/api/v2/tickets'
- If you are sure that your API key is correct, but are still unable to access your helpdesk, make sure that your "APIkey:X" is Base64-encoded before passing it as an "Authorization" header.
- Username/password basic authentication is deprecated as of May 31st 2023. See the solution here for more details.
What are the resources available via the API?
Every single piece of information - be it a customer's ID or the priority of a specific ticket - can be identified by its own unique identifier or "URI". If you want your data from the helpdesk, whether via your smartphone app or via a third party service, you need this identifier. All URIs follow a specific format and that format is:
https://your_helpdesk_domain_name/api/v2/resource_name
For example, if you are the admin of the Freshservice portal "acmeinc.freshservice.com", then to access the tickets in your helpdesk, the syntax would be
https://acmeinc.freshservice.com/api/v2/tickets
Note: We have shortened API resource URLs throughout this document by omitting the domain name. For example, /api/v2/tickets is actually https://domain.freshservice.com/api/v2/tickets
Will everyone have the same access rights?
No, everyone will not have the same access rights. Your ability to access data depends on the permissions available for your freshservice profile. If your freshservice Agent Role is "Newbie Agent" who is not allowed to answer to tickets, but is only allowed to view them, then the APIs will restrict you from answering and you'll only be able to view the tickets.
Schema
Blank Fields:
Blank fields are included as null instead of being omitted.
Timestamps:
All timestamps are returned in the UTC format, YYYY-MM-DDTHH:MM:SSZ. ( Example : 2016-02-13T23:27:49Z )
Date Fields:
Input for date fields is expected to be in one of the following formats:
YYYY-MM-DD
YYYY-MM-DDTHH:MM
YYYY-MM-DDTHH:MMZ
YYYY-MM-DDTHH:MM:SS
YYYY-MM-DDTHH:MM:SSZ
YYYY-MM-DDTHH:MM:SS±hh:mm
YYYY-MM-DDTHH:MM:SS±hh
YYYY-MM-DDTHH:MM:SS±hhmm
If the time zone information is not present, it will be assumed to be in UTC.
( some valid datefields : 2016-02-15T21:16:25Z, 2012-12-24T12:56:15+05:30, 2010-03-23T12:00 )
For more details on date format : ISO 8601
Location Header:
POST requests will contain the Location Header in the response that points to the URL of the created resource.
Response
HTTP STATUS: HTTP 201 Created
Headers:
"Location": https://domain.freshservice.com/api/v2/tickets/1
Embedding
Our previous version of APIs returned a large number of fields by default. In order to increase performance and reduce data usage, we have removed several of these fields in our v2.0 APIs. For example, when you view a ticket, we no longer return the requester's name or the company name. However, there may be situations where these fields are required and hence, we have included a mechanism to embed additional resources into an API call in order to minimise the number of required API calls.
Note: Embedding resources into an API that returns a single object will consume an additional API call credit per embedded resource while embedding into APIs that return a collection of objects will consume two additional credits.
You can request for additional resources using the "include" keyword. For example you can embed the requester's details within the ticket view API by using the following command
1 | curl -v -u 'abcdefgh12345678:X' -X GET 'https://domain.freshservice.com/api/v2/tickets/20?include=requester' |
Attachments
Attachments are supported for the following endpoints
Please follow the guidelines listed below
- Only files on your local machine can be attached using API.
- The Content-Type should always be multipart/form-data for create/update requests with attachments.
- The name of the file is preserved after it is attached i.e the filename sent in the response will be the same as the one in the request.
Errors
I have encountered an error. How do I debug it?
API requests that result in errors will return an appropriate HTTP status code to help you identify the type of error. You can use the table below to understand what each code means.
HTTP STATUS CODE | TEXT | DESCRIPTION |
---|---|---|
400 | Client or Validation Error | The request body/query string is not in the correct format. For example, the Create a ticket API requires the requester_id field to be sent as part of the request and if it is missing, this status code is returned. Also, requests containing a deprecated or invalid attribute will result in this error. For example, if ticket_scope, problem_scope or any of the deprecated attributes are sent in the API requests to /api/v2/agents then this error is returned. |
401 | Authentication Failure | Indicates that the Authorization header is either missing or incorrect. For example, if you send an API request containing username/password then authentication will fail with this error. You can learn more about the Authorization header here. |
403 | Access Denied | This indicates that the agent whose credentials were used for making this request was not authorized to perform this API call. It could be that this API call requires admin level credentials or perhaps the Freshservice portal doesn't have the corresponding feature enabled. It could also indicate that the user has reached the maximum number of failed login attempts or that the account has reached the maximum number of agents. |
404 | Requested Resource not Found | This status code is returned when the request contains invalid ID/Freshservice domain in the URL or an invalid URL itself. For example, an API call to retrieve a ticket with an invalid ID will return an HTTP 404 status code to let you know that no such ticket exists. |
405 | Method not allowed | This API request used the wrong HTTP verb/method. For example an API PUT request on /api/v2/tickets endpoint will return an HTTP 405 as /api/v2/tickets allows only GET and POST requests. |
406 | Unsupported Accept Header | Only application/json and */* are supported. When uploading files multipart/form-data is supported. |
409 | Inconsistent/Conflicting State | The resource that is being created/updated is in an inconsistent or conflicting state. |
415 | Unsupported Content-type | Content type application/xml is not supported. Only application/json is supported. |
429 | Rate Limit Exceeded | The API rate limit allotted for your Freshservice domain has been exhausted. |
500 | Unexpected Server Error | You can't do much here. This indicates an error at Freshservice's side. Please email us your script which invokes our API, along with the response headers. We will work with you to fix the issue. |
Error Response
In addition to the HTTP status code, most errors will also return a response body that contains more information to help you debug the error. A sample error response is shown below. The format of the error response body is explained after the example.
Error Response Fields
FIELD | DESCRIPTION |
---|---|
field | The request field that triggered this error. Applicable to HTTP 400 errors only. |
message | Detailed error message. |
code | Custom error code that is machine-parseable. |
Error Codes
In addition to the the error message, the error response will also contain an error code that is machine-parseable. The following table lists the error codes and their descriptions.
CODE | DESCRIPTION |
---|---|
missing_field | A mandatory attribute is missing. For example, calling Create a Ticket without the mandatory description in the request will result in this error. |
invalid_value | This code indicates that a request contained an incorrect or blank value, or was in an invalid format. |
duplicate_value | Indicates that this value already exists. |
datatype_mismatch | Indicates that the field value doesn't match the expected data type. For instance, entering text in a numerical field would trigger this error. |
invalid_field | An unexpected field was part of the request. If any additional field is included in the request payload (other than what is specified in the API documentation), this error will occur. |
invalid_json | Request parameter is not a valid JSON. We recommend that you validate the JSON payload with a JSON validator before firing the API request. |
invalid_credentials | Incorrect or missing API credentials. As the name suggests, it indicates that the API request was made with invalid credentials. Forgetting to apply Base64 encoding on the API key is a common cause of this error. |
access_denied | Insufficient privileges to perform this action. An agent attempting to access admin APIs will result in this error. |
require_feature | Not allowed since a specific feature has to be enabled in your Freshservice portal for you to perform this action. |
account_suspended | Account has been suspended. |
ssl_required | HTTPS is required in the API URL. |
readonly_field | Read only field cannot be altered. |
password_lockout | The agent has reached the maximum number of failed login attempts. |
password_expired | The agent's password has expired. |
no_content_required | No JSON data required. |
inaccessible_field | The agent is not authorized to update this field. |
incompatible_field | The field cannot be updated due to the current state of the record. |
unsupported_authentication_type | API request is made with an unsupported authentication type such as username/password. |
access_token_expired | API request is made with an expired Oauth access token. Obtain a new access token using the refresh token and retry the request. |
access_token_invalid | API request is made with Oauth token with invalid signature or invalid scope(s) or an account which is no longer part of the Freshworks organization for which the token was issued. |
Pagination
API responses that return a list of objects, such as View List of Tickets are paginated. To scroll through the pages, add the parameter page to the query string. The page number starts with 1.
https://domain.freshservice.com/api/v2/tickets?page=2
By default, the number of objects returned per page is 30. This can be adjusted by adding the per_page parameter to the query string. The maximum number of objects that can be retrieved per page is 100. Invalid values and values greater than 100 will result in an error.
https://domain.freshservice.com/api/v2/tickets?per_page=10
The per_page and page parameters can also be used together. The following example will retrieve the 11th to 20th tickets.
https://domain.freshservice.com/api/v2/tickets?per_page=10&page=2
The 'link' header in the response will hold URL of the next page, if it exists. If you have reached the last page of objects, then the link header will not be set.
Headers:
"link":< https://domain.freshservice.com/api/v2/tickets?filter=all_tickets&page=2>;rel="next"
Best Practices
Rate Limit
- Whenever possible, please queue API calls at your end. This ensures that you can buffer calls on your end to avoid hitting the rate limit and retry API calls when you hit the rate limit after the retry-after time.
- Cache non-volatile data on your end whenever it is feasible. For e.g. the mapping between agent name and ID is extremely unlikely to change. Hence, by caching it on the client side, you will be able to avoid API calls.
- As soon as you recognise that a rate limit increase will be required in the future, contact us. This will make it possible for us to ensure that we are prepared to increase the limit as and when needed.
Others
- Avoid making API calls directly from a mobile app. Instead, send the request to your servers and make the API calls from there. This ensures that in the event of an API endpoint being modified, you will be able to make and deploy the change to your server rather than updating your app and forcing your users to the latest version.
- Always use HTTP connection/multiplexing when making the API request. This will save some time while opening TCP connection to Freshservice.
- When retrieving a list of objects, avoid making calls referencing page numbers over 500 (deep pagination). These are performance intensive calls and you may suffer from extremely long response times.
API Index
Category | Create | View | View List | Update | Delete | Others |
---|---|---|---|---|---|---|
Tickets | Yes | Yes | Yes | Yes | Yes | 29 more |
Conversations | Yes | No | Yes | Yes | Yes | 2 more |
Problems | Yes | Yes | Yes | Yes | Yes | 18 more |
Changes | Yes | Yes | Yes | Yes | Yes | 18 more |
Releases | Yes | Yes | Yes | Yes | Yes | 19 more |
CABs | Yes | Yes | Yes | Yes | Yes | |
Workspaces | No | Yes | Yes | No | No | |
Approvals | No | No | Yes | No | No | |
Requesters | Yes | Yes | Yes | Yes | Yes | 7 more |
Agents | Yes | Yes | Yes | Yes | Yes | 6 more |
Agent Roles | No | Yes | Yes | No | No | |
Agent Groups | Yes | Yes | Yes | Yes | Yes | |
Requester Groups | Yes | Yes | Yes | Yes | Yes | 3 more |
Locations | Yes | Yes | Yes | Yes | Yes | 1 more |
Products | Yes | Yes | Yes | Yes | Yes | |
Vendors | Yes | Yes | Yes | Yes | Yes | |
Assets | Yes | Yes | Yes | Yes | Yes | 15 more |
Purchase Order | Yes | Yes | Yes | Yes | Yes | 1 more |
Asset Types | Yes | Yes | Yes | Yes | Yes | 1 more |
Software | Yes | Yes | Yes | Yes | Yes | 12 more |
Contracts | Yes | Yes | Yes | Yes | No | 10 more |
Departments | Yes | Yes | Yes | Yes | Yes | 2 more |
Business Hours | No | Yes | Yes | No | No | |
Projects | Yes | Yes | Yes | Yes | Yes | 2 more |
Project Tasks | Yes | Yes | Yes | Yes | Yes | |
Projects NewGen | Yes | Yes | Yes | Yes | Yes | 9 more |
Project Tasks NewGen | Yes | Yes | Yes | Yes | Yes | 17 more |
Solution Category | Yes | Yes | Yes | Yes | Yes | |
Solution Folder | Yes | Yes | Yes | Yes | Yes | 1 more |
Solution Article | Yes | Yes | Yes | Yes | Yes | 6 more |
Service Catalog | Yes | Yes | Yes | No | No | 2 more |
Announcements | Yes | Yes | Yes | Yes | Yes | |
Employee Onboarding | Yes | Yes | Yes | No | No | 2 more |
Employee Offboarding | Yes | Yes | Yes | No | No | 2 more |
Oncall management | Yes | Yes | Yes | Yes | Yes | 19 more |
Custom Objects | Yes | No | Yes | Yes | Yes | 2 more |
SLA Policies | No | No | Yes | No | No | |
Canned Responses | No | Yes | Yes | No | No | 3 more |
Audit Logs | No | No | No | No | No | 1 more |
Attachment | No | Yes | No | No | No | 1 more |
Tickets
This section lists all API that can be used to create, edit or otherwise manipulate tickets.
Attribute | Type | Description |
---|---|---|
id | number | Unique ID of the ticket. |
workspace_id | number | ID of the workspace that the ticket belongs to. If not provided, the ID of the primary workspace will be defaulted. Applicable only to accounts on the Employee Support Mode. |
attachments | array of objects | Ticket attachments. The total size of these attachments cannot exceed 40 MB. |
cc_emails | array of strings | Email addresses added in the 'cc' field of the incoming ticket email. |
department_id | number | ID of the department to which this ticket belongs. |
custom_fields | dictionary | Key value pairs containing the names and values of custom fields. Read more here. |
deleted | boolean | Set to true if the ticket has been deleted/trashed. Deleted tickets will not be displayed in any views except the "deleted" filter. |
description | string | HTML content of the ticket. |
description_text | string | Content of the ticket in plain text. |
due_by | datetime | Timestamp that denotes when the ticket is due to be resolved. |
string | Email address of the requester. If no contact exists with this email address in Freshservice, it will be added as a new contact. | |
email_config_id | number | ID of email config which is used for this ticket. (i.e., support@yourcompany.com/sales@yourcompany.com) |
fr_due_by | datetime | Timestamp that denotes when the first response is due. |
fr_escalated | boolean | Set to true if the ticket has been escalated as a result of the first response time being breached. |
fwd_emails | array of strings | Email addresses added while forwarding a ticket. |
group_id | number | ID of the group to which the ticket has been assigned. |
is_escalated | boolean | Set to true if the ticket has been escalated for any reason. |
name | string | Name of the requester. |
phone | string | Phone number of the requester. If no contact exists with this phone number in Freshservice, 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. |
priority | number | Priority of the ticket. |
category | number | Ticket Category. |
sub_category | string | Ticket sub category. |
item_category | string | Ticket item category. |
reply_cc_emails | array of strings | Email addresses added while replying to a ticket. |
requester_id | number | User ID of the requester. For existing contacts, the requester_id can be passed instead of the requester's email. |
responder_id | number | ID of the agent to whom the ticket has been assigned. |
source | number | The channel through which the ticket was created. |
spam | boolean | Set to true if the ticket has been marked as spam. |
status | number | Status of the ticket. |
subject | string | Subject of the ticket. |
tags | array of strings | Tags that have been associated with the ticket. |
to_emails | Array of strings | Email addresses to which the ticket was originally sent. |
type | string | Helps categorize the ticket according to the different kinds of issues your support team deals with. [Support for only type ‘incident’ as of now] |
created_at | datetime | Ticket creation timestamp. |
updated_at | datetime | Ticket updated timestamp. |
urgency | number | Ticket urgency. |
impact | number | Ticket impact. |
resolution_notes | string | Content of the ticket resolution note in plain text |
resolution_notes_html | string | HTML content of the ticket resolution note |
Ticket Properties
Every ticket uses certain fixed numerical values to denote its Status and Priorities. These numerical values along with their meanings are given below.
Source Type | Value |
---|---|
1 | |
Portal | 2 |
Phone | 3 |
Chat | 4 |
Feedback widget | 5 |
Yammer | 6 |
AWS Cloudwatch | 7 |
Pagerduty | 8 |
Walkup | 9 |
Slack | 10 |
Status | Value |
---|---|
Open | 2 |
Pending | 3 |
Resolved | 4 |
Closed | 5 |
Priorities | Value |
---|---|
Low | 1 |
Medium | 2 |
High | 3 |
Urgent | 4 |
Create a Ticket
This API helps you to create a new ticket in your service desk.
Ticket Properties
Every ticket uses certain fixed numerical values to denote its Status and Priorities. These numerical values along with their meanings are given below.
Source Type | Value |
---|---|
1 | |
Portal | 2 |
Phone | 3 |
Chat | 4 |
Feedback widget | 5 |
Yammer | 6 |
AWS Cloudwatch | 7 |
Pagerduty | 8 |
Walkup | 9 |
Slack | 10 |
Status | Value |
---|---|
Open | 2 |
Pending | 3 |
Resolved | 4 |
Closed | 5 |
Priorities | Value |
---|---|
Low | 1 |
Medium | 2 |
High | 3 |
Urgent | 4 |
1 | curl -v -u api_key:X -H "Content-Type: application/json" -d '{ "description": "Details about the issue...", "subject": "Support Needed...", "email": "tom@outerspace.com", "priority": 1, "status": 2, "cc_emails": ["ram@freshservice.com","diana@freshservice.com"], "workspace_id": 3 }' -X POST 'https://domain.freshservice.com/api/v2/tickets' |
Create a Ticket With Custom Fields
1 | curl -v -u api_key:X -H "Content-Type: application/json" -d '{ "description": "Details about the issue...", "subject": "Support Needed...", "email": "tom@outerspace.com", "priority": 1, "status": 2, "cc_emails": ["ram@freshservice.com","diana@freshservice.com"], "custom_fields" : { "custom_text" : "This is a custom text box" }, "workspace_id": 3 }' -X POST 'https://domain.freshservice.com/api/v2/tickets' |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 | { "ticket": { "cc_emails": [ "ram@freshservice.com", "diana@freshservice.com" ], "fwd_emails": [], "reply_cc_emails": [ "ram@freshservice.com", "diana@freshservice.com" ], "fr_escalated": false, "spam": false, "email_config_id": null, "group_id": null, "priority": 1, "requester_id": 1000000675, "requested_for_id": 1000000670, "responder_id": null, "source": 2, "status": 2, "subject": "Support Needed...", "to_emails": null, "department_id": null, "id": 265, "type": "Incident", "due_by": "2017-09-11T10:34:28Z", "fr_due_by": "2017-09-09T10:34:28Z", "is_escalated": false, "description": "<div>Details about the issue...</div>", "description_text": "Details about the issue...", "category": null, "sub_category": null, "item_category": null, "custom_fields": { "custom_text": "This is a custom text box", "auto_checkbox": null }, "created_at": "2017-09-08T10:34:28Z", "updated_at": "2017-09-08T10:34:28Z", "tags": [], "attachments": [], "workspace_id": 3, "resolution_notes": "Resolution note for the ticket...", "resolution_notes_html": "<div>Resolution note for the ticket...</div>" } } |
Create Ticket with attachment
Note:
1. This API request must have its Content-Type set to multipart/form-data.
2. For more information on attachment refer to this section.
1 | curl -v -u api_key:X -F 'attachments[]=@/Users/user/Desktop/api_attach.png' -F 'subject=Support Needed...' -F 'description=Details about the issue...' -F 'email=tom@outerspace.com' -F 'priority=1' -F 'status=2' -F 'workspace_id=3' -X POST 'https://domain.freshservice.com/api/v2/tickets' |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 | { "ticket": { "cc_emails": [], "fwd_emails": [], "reply_cc_emails": [], "fr_escalated": false, "spam": false, "email_config_id": null, "group_id": null, "priority": 1, "requester_id": 1232528431, "requested_for_id": 1000000670, "responder_id": null, "source": 2, "status": 2, "subject": "Support Needed...", "to_emails": null, "department_id": null, "id": 51, "type": "Incident", "due_by": "2021-04-22T06:01:08Z", "fr_due_by": "2021-04-15T03:01:08Z", "is_escalated": false, "description": "<div>Details about the issue...</div>", "description_text": "Details about the issue...", "category": null, "sub_category": null, "item_category": null, "custom_fields": { "new_number": null, "time_info": null, "number_test": null }, "created_at": "2021-04-12T06:01:08Z", "updated_at": "2021-04-12T06:01:08Z", "tags": [], "attachments": [ { "id": 368553, "content_type": "image/png", "size": 115399, "name": "api_attach.png", "attachment_url": "https://s3.amazonaws.com/cdn.freshgenie.com/data/helpdesk/attachments/production/19852343/original/api_attach.png", "created_at": "2021-04-12T06:01:08Z", "updated_at": "2021-04-12T06:01:08Z" } ], "workspace_id": 3, "resolution_notes": "Resolution note for the ticket...", "resolution_notes_html": "<div>Resolution note for the ticket...</div>" } } |
Create Ticket with assets
Note:
1. assets" key: contains comma (,) separated hash of the assets, each with key display id.
2. When "assets" is included as request parameter in PUT or POST request, the associated assets are returned implicitly in the response.
3. The existing request format to link a single asset ("associate_ci" : { "serial_no " : 123, "name " : "Andrea's Laptop " , "user ": "Andrea "}) will be deprecated soon.
4. If both "assets" and "associate_ci" keys are given in the request, assets key would be considered preferably and associate_ci would be ignored.
1 | curl -v -u api_key:X -H "Content-Type: application/json" -d '{ "description": "Create ticket with assets linked", "status": 2, "email": "sample@freshservice.com", "priority": 1, "subject": "Create ticket with assets linked", "assets": [{ "display_id": 8 }, { "display_id": 9 }] "workspace_id": 3}' -X POST 'https://domain.freshservice.com/api/v2/tickets' |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 | { "ticket": { "cc_emails": [], "fwd_emails": [], "reply_cc_emails": [], "fr_escalated": false, "spam": false, "email_config_id": null, "group_id": null, "priority": 1, "requester_id": 1, "requested_for_id": 1000000670, "responder_id": null, "source": 2, "status": 2, "subject": "Create ticket with assets linked", "to_emails": null, "department_id": null, "id": 433, "type": "Incident", "due_by": "2020-02-06T11:30:00Z", "fr_due_by": "2020-01-30T08:30:00Z", "is_escalated": false, "description": "<div>Create ticket with assets linked</div>", "description_text": "Create ticket with assets linked", "category": null, "sub_category": null, "item_category": null, "resolution_notes":null, "resolution_notes_html":null, "custom_fields": { }, "created_at": "2020-01-27T12:08:06Z", "updated_at": "2020-01-27T12:08:06Z", "tags": [], "attachments": [], "workspace_id": 3, "assets": [ { "name": "Dell Monitor", "description": null, "ci_type_id": 12, "impact": 1, "created": "2019-12-13T12:31:47+05:30", "updated": "2019-12-13T12:31:47+05:30", "user_id": null, "department_id": null, "assigned_on": null, "agent_id": null, "author_id": 2, "author_type": "User", "deleted": false, "display_id": 8, "salvage": null }, { "name": "Logitech Mouse", "description": null, "ci_type_id": 4, "impact": 1, "created": "2019-12-13T12:31:47+05:30", "updated": "2019-12-13T12:31:47+05:30", "user_id": null, "department_id": null, "assigned_on": null, "agent_id": null, "author_id": 2, "author_type": "User", "deleted": false, "display_id": 9, "salvage": null } ] } } |
Create Ticket with associations
1 | curl -v -u api_key:X -H "Content-Type: application/json" -d '{ "description": "Details about the issue...", "subject": "Support Needed...", "email": "tom@outerspace.com", "priority": 1, "status": 2, "problem": {"display_id": 2}, "change_initiating_ticket": {"display_id": 4}, "change_initiated_by_ticket": {"display_id": 5}, "workspace_id": 3 }' -X POST 'https://domain.freshservice.com/api/v2/tickets' |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 | { "ticket": { "cc_emails": [], "fwd_emails": [], "reply_cc_emails": [], "fr_escalated": false, "spam": false, "email_config_id": null, "group_id": null, "priority": 1, "requester_id": 1232695482, "requested_for_id": 1000000670, "responder_id": null, "source": 2, "status": 2, "subject": "Support Needed...", "to_emails": null, "department_id": null, "id": 78, "type": "Incident", "due_by": "2021-04-30T10:39:46Z", "fr_due_by": "2021-04-28T10:39:46Z", "is_escalated": false, "description": "<div>Details about the issue...</div>", "description_text": "Details about the issue...", "category": null, "sub_category": null, "item_category": null, "custom_fields": { "deve": null, "locaite": null }, "created_at": "2021-04-27T10:39:46Z", "updated_at": "2021-04-27T10:39:46Z", "tags": [], "attachments": [], "workspace_id": 3, "problem": { "subject": "Unable to reach email server", "priority": 1, "status": 1, "impact": 1, "due_by": "2021-04-29T10:24:00Z", "display_id": 2, "requester_id": 1001536865, "owner_id": 1232265829, "group_id": null, "change_id": null, "deleted": false, "known_error": false, "created_at": "2021-04-27T10:25:20Z", "updated_at": "2021-04-27T10:25:20Z", "department_id": null, "email_config_id": null, "category": null, "sub_category": null, "item_category": null }, "change_initiating_ticket": { "display_id": 4, "requester_id": 1001536865, "owner_id": 1232265829, "group_id": null, "release_id": null, "priority": 1, "impact": 1, "status": 1, "risk": 1, "change_type": 1, "approval_status": 4, "deleted": false, "subject": "Getting ES3 back up to speed", "created_at": "2021-04-27T10:26:54Z", "updated_at": "2021-04-27T10:26:54Z", "cc_email": {}, "planned_start_date": "2021-04-19T18:45:00Z", "planned_end_date": "2021-04-19T23:15:00Z", "department_id": null, "email_config_id": null, "category": null, "sub_category": null, "item_category": null }, "change_initiated_by_ticket": { "display_id": 5, "requester_id": 1001536865, "owner_id": 1232265829, "group_id": null, "release_id": null, "priority": 1, "impact": 1, "status": 1, "risk": 1, "change_type": 1, "approval_status": 4, "deleted": false, "subject": "Upgrade Web Server", "created_at": "2021-04-27T10:28:48Z", "updated_at": "2021-04-27T10:28:48Z", "cc_email": {}, "planned_start_date": "2021-04-21T01:00:00Z", "planned_end_date": "2021-04-21T05:30:00Z", "department_id": 683112, "email_config_id": null, "category": null, "sub_category": null, "item_category": null } } } |
View a Ticket
Use 'include' to embed additional details in the response. Each include will consume an additional credit. For example if you embed the requester and company information you will be charged a total of 3 API credits for the call.
Note:
By default, certain fields such as conversations, tags and requester email will not be included in the response. They can be retrieved via the embedding functionality.
Embed | Handle |
---|---|
conversations | /api/v2/tickets/[id]?include=conversations Will return up to ten conversations sorted by "created_at" in ascending order. Including conversations will consume two API calls. In order to access more than ten conversations belonging to a ticket, use the List All Conversationsof a Ticket API. |
requester | /api/v2/tickets/[id]?include=requester Will return requester details like id, name, mobile, phone |
requested_for | /api/v2/tickets/[id]?include=requested_for Will return details of the user on behalf of whom the request has been raised |
stats | /api/v2/tickets/[id]?include=stats Will return the ticket’s closed_at, resolved_at and first_responded_at time |
problem | /api/v2/tickets/[id]?include=problem Returns details of associated problem |
assets | /api/v2/tickets/[id]?include=assets Returns set of associated asset details |
changes | /api/v2/tickets/[id]?include=changes Returns list of associated changes and causing changes details |
related_tickets | /api/v2/tickets/[id]?include=related_tickets Returns child ticket ids / parent ticket ids based on ticket. No ids returned for parent tickets with no children |
onboarding_context | /api/v2/tickets/[id]?include=onboarding_context Returns onboarding data mapped to the ticket |
offboarding_context | /api/v2/tickets/[id]?include=offboarding_context Returns offboarding data mapped to the ticket |
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X GET 'https://domain.freshservice.com/api/v2/tickets/20' |
1. Get the associated conversations along with the ticket response.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/20?include=conversations' |
2. Get the associated tags and requester information along with the ticket response.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/20?include=tags,requester' |
3. Get the associated stats information along with the ticket response.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/20?include=stats' |
4. Get the associated onboarding information along with the ticket response.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/20?include=onboarding_context' |
5. Get the associated offboarding information along with the ticket response.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/20?include=offboarding_context' |
Filter Tickets
Custom ticket fields that you have created in your account can also be used to filter through the tickets and get a list of tickets matching the specified ticket fields.
Query Format(query) - "(ticket_field:integer OR ticket_field:'string') AND ticket_field:boolean"
Note:
1. The query must be URL encoded
2. Query can be framed using the ticket field name in snake case, which can be obtained from Ticket Fields endpoint. Ticket Fields are case sensitive
3. Query string must be enclosed between a pair of double quotes and can have up to 512 characters
4. Logical operators AND, OR along with parentheses () can be used to group conditions
5. Relational operators greater than or equal to :> and less than or equal to :< can be used along with date fields and numeric fields
6. Input for date fields should be in UTC Format
7. The number of objects returned per page is 30 also the total count of the results will be returned along with the result
8. To scroll through the pages add page parameter to the url
9. To filter for agent and group with no values assigned, use the null keyword
10. By default, only tickets from the primary workspace will be returned for accounts on the Employee Support Mode. For tickets from other workspaces, use the workspace_id query parameter.
Supported Ticket Fields
Field | Type | Description |
---|---|---|
workspace_id | number | Workspace ID of the ticket. This attribute is applicable only to accounts on the Employee Support Mode. The value 0 for workspace_id will return tickets from all workspaces, with only global level fields. |
requester_id | number | User ID of the requester |
string | Email address of the requester | |
agent_id | number | ID of the agent to whom the ticket has been assigned |
group_id | number | ID of the group to which the ticket has been assigned |
priority | number | Priority of the ticket |
status | number | Status of the ticket |
impact | number | Ticket impact |
urgency | number | Ticket urgency |
tag | string | Tag that has been associated to the tickets |
due_by | date | Date (YYYY-MM-DD) when the ticket is due to be resolved |
fr_due_by | date | Date (YYYY-MM-DD) when the first response is due |
created_at | date | Ticket creation date (YYYY-MM-DD) |
Custom Fields
Field Type | Type |
---|---|
Number | number |
Checkbox | boolean |
Dropdown | string |
Date | date(YYYY-MM-DD) |
Note:
Queries can be combined using AND or OR.
https://domain.freshservice.com/api/v2/tickets/filter?query="priority: 1 AND status: 2 OR urgency: 3"
Supported operators 1. priority: 1 (priority equal to 1)
2. priority:> 1 (priority greater than or equal to 1)
3. priority :< 1 (priority less than or equal to 1)
Formatting 1. String fields to be enclosed in single quotes ('')
2. Number fields to be given as number without quotes.
3. Date and date_time fields to be enclosed in single quotes('yyyy-mm-dd')
4. only :> and :< are supported for date and date_time fields. Both fields expect input in the same format as 'yyyy-mm-dd'
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/filter?query="priority:3"' |
1. Get the list of Urgent and High priority tickets ('priority:4 OR priority:3')
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/filter?query="priority:4%20OR%20priority:3"' |
2. Get the second page of Open and Pending tickets ('status:3 OR status:4')
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/filter?query="status:3%20OR%20status:4"&page=2' |
3. Get the list of Urgent and High priority tickets in Open Status belong to the group_id 11 ('priority:3 AND group_id:11 AND status:2')
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/filter?query="priority:>3%20AND%20group_id:11%20AND%20status:2"' |
4. Get the list of tickets having Custom Dropdown selected as First Choice or Custom Checkbox false (Custom Fields: custom_dropdown, custom_checkbox) '(custom_dropdown:'First Choice' OR custom_checkbox: true)'
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/filter?query="custom_dropdown:%27First%20Choice%27%20OR%20custom_checkbox:true"' |
5. Get the list of Urgent priority tickets created after a particular day ("priority:4 AND created_at:>'2021-01-01'")
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/filter?query="%20priorIty:%203%20AND%20created_at:%3E%272020-01-01%27%20AND%20created_at:%3C%272021-01-01%27"' |
6. Get list of tickets with tag abc ("tag: 'abc'")
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/filter?query="tag:%27abc%27"' |
7. Get list of tickets with no agent assigned ('agent_id: null') from a particular workspace
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/filter?workspace_id=2&query="agent_id%3Anull"' |
8. Get the list of Urgent and High priority tickets ('priority:4 OR priority:3') from all accessible workspaces
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/filter?workspace_id=0&query="priority%3A4%20OR%20priority%3A3"' |
View List of Tickets
Use filters to view only specific tickets (those which match the criteria that you choose). By default only tickets that have not been deleted or marked as spam will be returned, unless you use the 'deleted' filter.
Note:
1. By default only tickets that have been created within the past 30 days will be returned. For older tickets, use the updated_since filter.
2. Use 'include' to embed additional details in the response. Each include will consume an additional 2 credits. For example if you embed the stats information you will be charged a total of 3 API credits (1 credit for the API call, and 2 credits for the additional stats embedding).
3. If a workspace_id is not specified as a URL parameter, only tickets from the primary workspace will be included in the response. If workspace_id is specified as 0, tickets from across all workspaces will be included in the response with just the global fields. Applicable only to accounts on the Employee Support Mode.
Filter by | Handle |
---|---|
Predefined filters | /api/v2/tickets?filter=[filter_name] The filters available are new_and_my_open, watching, spam, deleted. |
Requester | /api/v2/tickets?requester_id=[id] /api/v2/tickets?email=[requester_email] Example: /api/v2/tickets?email=superman@freshservice.com /api/v2/tickets?email=bat%2Bman%40gmail.com (URL encoded bat+man@gmail.com) |
Updated since | /api/v2/tickets?updated_since=2015-01-19T02:00:00Z |
Type | For Incidents: /api/v2/tickets?type=Incident For Service Requests: /api/v2/tickets?type=Service+Request |
Workspace | /api/v2/tickets?workspace_id=2 |
Sort by | Handle |
---|---|
asc, desc | /api/v2/tickets?order_type=asc Default sort order type is desc |
Embed | Handle |
---|---|
stats | /api/v2/tickets?include=stats Will return the ticket’s closed_at, resolved_at and first_responded_at time. |
Requester | /api/v2/tickets?include=requester Will return the requester's email, id, mobile, name, and phone. |
Requested For | /api/v2/tickets?include=requested_for Will return details of the user on behalf of whom the request has been raised |
onboarding_context | /api/v2/tickets?include=onboarding_context Will return details of the onboarding data mapped to the ticket |
offboarding_context | /api/v2/tickets?include=offboarding_context Will return details of the offboarding data mapped to the ticket |
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets' |
1. Get the first page of a list of tickets that are being watched by the agent whose credentials were used to make this API call.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets?filter=watching' |
2. Get the first page of a list of tickets from the specified requestor. The tickets will be returned in the descending order.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets?requester_id=1230&order_type=desc' |
3. Get the second page (tickets from 11-20) of a list of all tickets.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets?per_page=10&page=2' |
4. Get the first page of a list of tickets that have shown any activity since the 17th of August, 2015.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets?updated_since=2015-08-17' |
5. Get the associated stats information along with the ticket response.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets?include=stats' |
6. Filter tickets based on the following requester email (super+man@gmail.com) which needs to be URL encoded.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets?email=super%2Bman%40gmail.com' |
7. Get the list of all tickets from workspaces to which the user has access.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets?workspace_id=0' |
8. Get the list of tickets from a specific workspace
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets?workspace_id=3' |
Update a Ticket
This API lets you make changes to the parameters of a ticket from updating statuses to changing ticket type.
Note:
1. While updating tags, all the tags that need to stay associated with the Ticket should be provided in the PUT request payload.
2. The requested_for_id field can be updated only for Service Request tickets.
3. The workspace_id attribute cannot be updated through the Update operation. It can only be updated through the Move operation.
Query Parameters | Handle |
---|---|
bypass_mandatory | To bypass mandatory fields check while updating the ticket except for requester_id, source. Any business rules trying to mandate certain fields will also be bypassed. All fields configured as mandatory upon closing or resolving the ticket will be skipped while updating the ticket. This can only be passed by an admin. Example: api/v2/ticket/{ticket_id}?bypass_mandatory=true |
Ticket Properties
Every ticket uses certain fixed numerical values to denote its Source, Status, and Priorities. These numerical values along with their meanings are given below.
Source Type | Value |
---|---|
1 | |
Portal | 2 |
Phone | 3 |
Chat | 4 |
Feedback widget | 5 |
Yammer | 6 |
AWS Cloudwatch | 7 |
Pagerduty | 8 |
Walkup | 9 |
Slack | 10 |
Status | Value |
---|---|
Open | 2 |
Pending | 3 |
Resolved | 4 |
Closed | 5 |
Priorities | Value |
---|---|
Low | 1 |
Medium | 2 |
High | 3 |
Urgent | 4 |
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X PUT -d '{ "priority": 3 }' 'https://domain.freshservice.com/api/v2/tickets/1' |
Update Ticket with attachment
Note:
1. This API request must have its Content-Type set to multipart/form-data.
2. For more information on attachment refer to this section.
1 | curl -v -u api_key:X -F 'attachments[]=@/Users/user/Desktop/api2.png' -F 'priority=1' -X PUT 'https://domain.freshservice.com/api/v2/tickets/51' |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 | { "ticket": { "cc_emails": [], "fwd_emails": [], "reply_cc_emails": [], "spam": false, "email_config_id": null, "fr_escalated": false, "group_id": null, "priority": 1, "requester_id": 1232528431, "requested_for_id": 1000000670, "responder_id": null, "source": 2, "status": 2, "subject": "Support Needed...", "description": "<div>Details about the issue...</div>", "description_text": "Details about the issue...", "category": null, "sub_category": null, "item_category": null, "custom_fields": { "new_number": null, "time_info": null, "number_test": null }, "id": 51, "type": "Incident", "to_emails": null, "department_id": null, "is_escalated": false, "tags": [], "due_by": "2021-04-22T06:01:08Z", "fr_due_by": "2021-04-15T03:01:08Z", "created_at": "2021-04-12T06:01:08Z", "updated_at": "2021-04-12T06:01:08Z", "resolution_notes":null, "resolution_notes_html":null, "attachments": [ { "id": 368553, "content_type": "image/png", "size": 115399, "name": "api_attach.png", "attachment_url": "https://s3.amazonaws.com/cdn.freshgenie.com/data/helpdesk/attachments/production/19852343/original/api_attach.png", "created_at": "2021-04-12T06:01:08Z", "updated_at": "2021-04-12T06:01:08Z" }, { "id": 368554, "content_type": "image/png", "size": 274688, "name": "api2.png", "attachment_url": "https://s3.amazonaws.com/cdn.freshgenie.com/data/helpdesk/attachments/production/19852343/original/api2.png", "created_at": "2021-04-12T06:26:40Z", "updated_at": "2021-04-12T06:26:40Z" } ], "workspace_id": 3 } } |
Update Ticket with assets
Note:
1. Existing assets, if they are different from what are given in request, are destroyed and the current ones are linked to the ticket. So, all the assets that need to stay associated with the Ticket need to be provided in the PUT/POST calls
2. "assets" key: contains comma (,) separated hash of the assets, each with key display id.
3. When "assets" is included as request parameter in PUT or POST request, the associated assets are returned implicitly in the response.
4. The existing request format to link a single asset ("associate_ci" : { "serial_no " : 123, "name " : "Andrea's Laptop " , "user ": "Andrea "}) will be deprecated soon.
5. If both "assets" and "associate_ci" keys are given in the request, assets key would be considered preferably and associate_ci would be ignored.
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X PUT -d '{ "description": "Update ticket with assets", "status": 2, "email": "sample@freshservice.com", "priority": 1, "subject": "Update ticket with assets", "assets": [ { "display_id": 7 }, { "display_id": 8 }]}' 'https://domain.freshservice.com/api/v2/tickets/1' |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 | { "ticket": { "cc_emails": [], "fwd_emails": [], "reply_cc_emails": [], "spam": false, "email_config_id": null, "fr_escalated": false, "group_id": null, "priority": 1, "requester_id": 1, "requested_for_id": 1000000670, "responder_id": null, "source": 2, "status": 2, "subject": "Update ticket with assets", "description": "Update ticket with assets", "description_text": "Update ticket with assets", "category": null, "sub_category": null, "item_category": null, "custom_fields": {}, "id": 433, "type": "Incident", "to_emails": null, "department_id": null, "is_escalated": false, "tags": [], "due_by": "2020-02-06T17:00:00+05:30", "fr_due_by": "2020-01-30T14:00:00+05:30", "created_at": "2020-01-27T12:08:06Z", "updated_at": "2020-01-27T12:13:39Z", "attachments": [], "workspace_id": 3, "resolution_notes":null, "resolution_notes_html":null, "assets": [ { "name": "Andrea's Laptop", "description": null, "ci_type_id": 25, "impact": 2, "created": "2019-12-13T12:31:47+05:30", "updated": "2019-12-13T12:31:47+05:30", "user_id": 2, "department_id": null, "assigned_on": null, "agent_id": null, "author_id": 2, "author_type": "User", "deleted": false, "display_id": 7, "salvage": null }, { "name": "Dell Monitor", "description": null, "ci_type_id": 12, "impact": 1, "created": "2019-12-13T12:31:47+05:30", "updated": "2019-12-13T12:31:47+05:30", "user_id": null, "department_id": null, "assigned_on": null, "agent_id": null, "author_id": 2, "author_type": "User", "deleted": false, "display_id": 8, "salvage": null } ] } } |
Move a Ticket
This API moves a ticket to a different workspace, while also allowing the assigned group and agent to be modified.
Note:
This endpoint is applicable only to accounts on the Employee Support Mode.
1 | curl -v -u api_key:X -X PUT -d '{ "workspace_id": 3, "group_id": 3, "responder_id": 4 }' 'https://domain.freshservice.com/api/v2/tickets/1/move_workspace' |
Delete a Ticket
This API helps you delete a ticket.
Note:
1. Deleted tickets are not permanently lost. You can retrieve them using the Restore Ticket API.
2. When a parent SR is deleted all the child tickets will also be deleted.
1 | curl -v -u api_key:X -X DELETE 'https://domain.freshservice.com/api/v2/tickets/1' |
Delete a Ticket Attachment
This API helps you delete an attachment from a ticket.
1 | curl -v -u api_key:X -X DELETE 'https://domain.freshservice.com/api/v2/tickets/1/attachments/1' |
Restore a Ticket
The API mentioned previously. If you deleted some tickets and regret doing so now, this API will help you restore them.
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X PUT -d '' 'https://domain.freshservice.com/api/v2/tickets/1/restore' |
Create a Child Ticket
This API lets you to create a new child ticket on an existing ticket
Note:
1. Association of child tickets is not available in the Sprout plan.
2. Association of child tickets to a deleted or a spammed ticket is not allowed.
3. Nesting of a child ticket under another child ticket is not supported.
Attribute | Type | Description |
---|---|---|
workspace_id | number | ID of the workspace to which this ticket belongs. This attribute is applicable only to accounts on the Employee Support Mode. The default value is the ID of the parent ticket's workspace. |
name | string | Name of the requester |
requester_id * | number | User ID of the requester. For existing contacts, the requester_id can be passed instead of the requester's email. |
email * | string | Email address of the requester. If no contact exists with this email address in Freshservice, it will be added as a new contact. |
phone * | string | Phone number of the requester. If no contact exists with this phone number in Freshservice, 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. |
subject | string | Subject of the ticket. The default value is null. |
type | string | Helps categorize the ticket according to the different kinds of issues your support team deals with. The default Value is incident. * As of now, API v2 supports only type ‘incident’ |
status * | number | Status of the ticket. |
priority * | number | Priority of the ticket. |
description | string | HTML content of the ticket. |
responder_id | number | ID of the agent to whom the ticket has been assigned |
attachments | array of objects | Ticket attachments. The total size of these attachments cannot exceed 40 MB. |
cc_emails | array of strings | Email address added in the 'cc' field of the incoming ticket email. |
custom_fields | dictionary | Key value pairs containing the names and values of custom fields. Read more here. |
due_by | datetime | Timestamp that denotes when the ticket is due to be resolved. |
email_config_id | number | ID of email config which is used for this ticket. (i.e., support@yourcompany.com/sales@yourcompany.com) |
fr_due_by | datetime | Timestamp that denotes when the first response is due |
group_id | number | ID of the group to which the ticket has been assigned. The default value is the ID of the group that is associated with the given email_config_id |
source * | number | The channel through which the ticket was created. The default value is 2. |
tags | array of strings | Tags that have been associated with the ticket |
department_id | number | Department ID of the requester. |
category | string | Ticket category |
sub_category | string | Ticket sub category |
item_category | string | Ticket item category |
associate_ci | hash | Search for asset and associate with ticket |
urgency | number | Ticket urgency |
impact | number | Ticket impact |
* Refer to the Ticket properties table for supported values. * Any of the five attributes is mandatory. |
Ticket Properties
Every ticket uses certain fixed numerical values to denote its Status and Priorities. These numerical values along with their meanings are given below.
Source Type | Value |
---|---|
1 | |
Portal | 2 |
Phone | 3 |
Chat | 4 |
Feedback widget | 5 |
Yammer | 6 |
AWS Cloudwatch | 7 |
Pagerduty | 8 |
Walkup | 9 |
Slack | 10 |
Status | Value |
---|---|
Open | 2 |
Pending | 3 |
Resolved | 4 |
Closed | 5 |
Priorities | Value |
---|---|
Low | 1 |
Medium | 2 |
High | 3 |
Urgent | 4 |
1 | curl -v -u api_key:X -H "Content-Type: application/json" -d '{ "description": "Details about the issue...", "subject": "Support Needed...", "email": "tom@outerspace.com", "priority": 1, "status": 2, "cc_emails": ["ram@freshservice.com","diana@freshservice.com"], "workspace_id": 3 }' -X POST 'https://domain.freshservice.com/api/v2/tickets/20/create_child_ticket' |
List All Ticket Fields
Retrieve all the Fields that constitute the Ticket Object
Note:
By default, only global fields and fields from the primary workspace will be returned for accounts on the Employee Support Mode. For fields from other workspaces, use the workspace_id filter.
Change field | Description |
---|---|
id | Unique ID of the Field |
workspace_id | ID of the workspace to which this ticket field belongs. This attribute is applicable only to accounts on the Employee Support Mode. |
created_at | Date time at which the field was added |
updated_at | Date time at which the field was modified |
name | Name of the field |
label | Label of the field for display |
description | Description of the field |
field_type | Indicates if the field is a checkbox, dropdown, text field |
required | True if the field is marked mandatory |
required_for_closure | True if the field is marked mandatory while closing the Release item |
default_field | True if the field is a default field. False if customm |
choices | List of values supported by the field |
nested_fields | contain details of nested fields |
required_for_agents | Set to true if the field is mandatory for Agents |
required_for_customers | Set to true if the field is mandatory in the customer portal |
label_for_customers | Display name for the field (as seen in the customer portal) |
customers_can_edit | Set to true if the field can be updated by customers |
displayed_to_customers | Set to true if the field is displayed in the customer portal |
portal_cc | Applicable only for the requester field. Set to true if customer can add additional requesters to a ticket |
portal_cc_to | Applicable only if portal_cc is set to true. Value will be all when a customer can add any requester to the CC list and company when a customer can add only company contacts to the CC list |
date_only | Applicable only for custom_date field. When ‘Request time information’ is selected, the field date_only returns false and if unchecked, date_only returns true |
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/ticket_form_fields' |
1. Get the list of ticket fields from a specific workspace
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/ticket_form_fields?workspace_id=2' |
Get Ticket Activites
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X GET 'https://domain.freshservice.com/api/v2/tickets/152/activities' |
Time Entries
These APIs help to track exactly how much time an agent has spent on each ticket, start/stop timers and perform a lot of other time tracking and monitoring tasks to ensure that the support team is always performing at its peak efficiency.
Attribute | Type | Description |
---|---|---|
id | Number | Id of the time entry READ-ONLY |
workspace_id | Number | ID of the workspace to which the time entry belongs(inherited from the ticket's workspace). This attribute is applicable only to accounts on the Employee Support Mode. READ-ONLY |
created_at | DateTime | Time at which this time-entry is created READ-ONLY |
updated_at | DateTime | Time at which the time-entry is updated READ-ONLY |
start_time | DateTime | The time at which the time-entry is added. If a timer, which is in stopped state, is started again, this holds date_time at which the timer is started again READ-ONLY |
timer_running | Boolean | Set to true if timer is currently running. Default value is false. At a time, only one timer can be running for an agent across the account |
billable | Boolean | Set as true if the time-entry is billable. Default value is true |
time_spent | String | The total amount of time spent by the timer in hh::mm format. This field cannot be set if timer_running is true. Mandatory if timer_running is false |
executed_at | DateTime | Time at which the timer is executed. Default value (unless given in request) is the time at which timer is added. Should be less than or equal to current date_time |
task_id | Number | Id of the task assigned to the time-entry. Task should be valid on the given ticket and assigned to agent_id |
note | String | Description of the time-entry |
agent_id | Number | The user/agent to whom this time-entry is assigned MANDATORY |
Create a Time Entry
This API helps to create a Time Entry.
Note:
1. If timer_running is not specified in the request, it is considered as false and time_spent is mandatory in this scenario.
2. time_spent can be set only if timer_running is false or not set.
1 | curl -v -u api_key:X -H "Content-Type: application/json" -d '{"time_entry":{"note":"test_entry","time_spent":"03:00","agent_id":1}}' -X POST 'https://domain.freshservice.com/api/v2/tickets/1/time_entries' |
1. Create a time-entry along with time spent value. Timer will not be started
1 | curl -v -u api_key:X -H 'Content-Type: application/json' -d '{"time_entry":{"note":"test_entry","time_spent":"03:00","agent_id":1}}' -X POST 'https://domain.freshservice.com/api/v2/tickets/1/time_entries' |
2. Create a time-entry with timer running
1 | curl -v -u api_key:X -H 'Content-Type: application/json' -d '{"time_entry":{"note":"test_entry","timer_running":true,"agent_id":1}}' -X POST 'https://domain.freshservice.com/api/v2/tickets/1/time_entries' |
View a Time Entry
This API call helps to list a particular Time Entry.
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X GET 'https://domain.freshservice.com/api/v2/tickets/1/time_entries/20' |
List All Time Entries of a Ticket
This API helps to view all time entries of a particular ticket.
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X GET 'https://domain.freshservice.com/api/v2/tickets/1/time_entries' |
Update a Time Entry
This API can be used to update/modify existing time entry.
Note:
1. For a running timer, time_spent cannot be updated without stopping it.
Attribute | Type | Description |
---|---|---|
id | Number | Id of the time entry READ-ONLY |
workspace_id | Number | Workspace ID of the time entry(inherited from the ticket). This attribute is applicable only to accounts on the Employee Support Mode. READ-ONLY |
created_at | DateTime | Time at which this time-entry is created READ-ONLY |
updated_at | DateTime | Time at which this time-entry is updated READ-ONLY |
start_time | DateTime | The time at which the time-entry is added. If a timer, which is in stopped state, is started again, date_time at which the timer is started again READ-ONLY |
timer_running | Boolean | Cannot update timer_running to the same existing value. |
billable | Boolean | Can be set to true or false |
time_spent | String | The total amount of time spent by the timer in hh::mm format. |
executed_at | DateTime | Time at which the timer is executed. Default value (unless given in request) is the time at which timer is added. Should be less than or equal to current date_time. |
task_id | Number | Id of the task assigned to the time-entry. Task should be valid on the given ticket and should be assigned to the agent_id |
note | String | Description of the time-entry |
agent_id | Number | The user/agent to whom this time-entry is to be assigned MANDATORY |
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X PUT -d '{"time_entry":{"note":"text_update","agent_id":1}}' 'https://domain.freshservice.com/api/v2/tickets/1/time_entries/20' |
Delete a Time Entry
This API can be used to delete an existing Time Entry. Deleted time entries cannot be restored.
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X DELETE 'https://domain.freshservice.com/api/v2/tickets/1/time_entries/20' |
Create a Source
This API helps you create a new Ticket Source.
Attribute | Type | Description |
---|---|---|
name | string | Name of the source |
1 | curl -v -u api_key:X -H "Content-Type: application/json" -d '{ "name": "Source Name" }' -X POST 'https://domain.freshservice.com/api/v2/ticket_fields/sources' |
Service Request
This section lists all API that are related to service requests
Create a Service Request
This API helps you create a service request
Note 1:
The service requested will be created with the requester specified in “email” attribute. If no email is provided, the request is created on behalf of the agent
Note 2:
Fields in the API behave like the agent portal's new service request page. If a field is not visible in self service portal, you can still provide a value for that field using the api. If a field is marked mandatory but not visible in portal in service item, you must provide a value for it in the api.
Request Attrubutes
Attribute | Type | Description |
---|---|---|
quantity | number | Quantity needed by the requested |
requested_for | Email id of the requester on whose behalf the service request is created | |
Email id of the requester | ||
child_items | - | Service items that are included as child items. Provide the display id as service_item_id for each child item. |
custom_fields | - | Values of custom fields present in the service item form |
Response Attrubutes
Attribute | Type | Description |
---|---|---|
Ticket Attributes | - | Refer to Ticket attributes for complete list here |
requested_items | - | Items requested as part of service request |
approval_status | number | Current approval status of the service request. ‘1’ if approved, ‘2’ if rejected |
approval_status_name | string | Display name of the approval status |
custom_fields | - | Custom fields present in the ticket form |
1 | curl -v -u api_key:X -H "Content-Type: application/json" -d '{"email": "tom@outerspace.com", “quantity” : 1 }' -X POST 'https://domain.freshservice.com/api/v2/service_catalog/items/1/place_request' |
Create a Child Service Request
This API helps you to create a new child ticket on an existing ticket
Note 1:
Association of child Service Request to a deleted or a spammed ticket is not allowed.
Note 2:
Nesting of a child Service Request under another child Service Request is not supported.
Request Attributes
Attribute | Type | Description |
---|---|---|
quantity | number | Quantity needed by the requested |
requested_for | Email id of the requester on whose behalf the service request is created | |
Email id of the requester | ||
child_items | - | Service items that are included as child items. Provide the display id as service_item_id for each child item. |
custom_fields | - | Values of custom fields present in the service item form |
parent_ticket_id | number | Display ID of the parent Service Request/Case/Query/Issue/Request/Incident/Major Incident |
Response Attributes
Attribute | Type | Description |
---|---|---|
Ticket Attributes | - | Refer to Ticket attributes for complete list here |
requested_items | - | Items requested as part of service request |
approval_status | number | Current approval status of the service request. ‘1’ if approved, ‘2’ if rejected |
approval_status_name | string | Display name of the approval status |
custom_fields | - | Custom fields present in the ticket form |
1 | curl -v -u api_key:X -H "Content-Type: application/json" -d '{"email": "tom@outerspace.com", “quantity” : 1 , "parent_ticket_id":17894}' -X POST 'https://domain.freshservice.com/api/v2/service_catalog/items/1/place_request' |
View Requested Items of a Service Request
This api helps you to view requested items attached to a service request
Attribute | Type | Description |
---|---|---|
id | number | Unique id of the requested item |
created_at | datetime | Timestamp at which the requested item was attached to service request |
updated_at | datetime | Timestamp at which the requested item was updated in the service request |
quantity | number | Number of units of the item needed by the requester. By default it is 1 |
stage | number | Current stage of the requested item |
loaned | boolean | Indicated whether the requested item is a loaner item |
cost_per_request | number | Cost of the requested service item |
remarks | string | Remarks related to a requested item |
delivery_time | number | Estimated delivery time (in hrs) |
is_parent | boolean | Boolean indicating whether this is the parent service item |
service_item_id | number | Display id of service item unique to your account |
Stages
Stage | Value |
---|---|
Requested | 1 |
Delivered | 2 |
Cancelled | 3 |
Fulfilled | 4 |
Partially Fulfilled | 5 |
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X GET 'https://domain.freshservice.com/api/v2/tickets/1/requested_items' |
Update Requested Items of a Service Request
This api helps you to update the requested items attached to a service request
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X PUT -d '{"quantity":2, "stage":2, "custom_fields":{"additional_property_1": "value1"}}' 'https://domain.freshservice.com/api/v2/tickets/1/requested_items/1' |
Approvals
This section lists all API that can be used to create, edit or otherwise manipulate Service Request Approvals.
Attribute | Type | Description |
---|---|---|
id | number | Unique ID of the approval |
created_at | datetime | Approval creation timestamp |
updated_at | datetime | Approval updated timestamp |
approver_id | number | User ID of the approver |
approver_name | string | Name of the approver |
approval_type | number | Helps define the type of approval in case there are more than one approvers |
user_id | number | User ID of the initiator of the approval |
user_name | string | Name of the initiator of the approval |
level | number | Indicates the level information for multi-level approvals |
approval_status | hash | Status ID and Name of the approval |
delegatee | hash | User ID and Name of the delegatee for the approval |
latest_remark | string | Remarks given by the approver |
email_content | string | HTML content of the approval email (only available for “Request Approval” and “View an Approval” APIs) |
Approval Properties
Approvals use certain fixed numerical values to denote its status and types. These numerical values along with their meanings are given below:
Approval Type | Value |
---|---|
To be approved by Everyone | 1 |
To be approved by Anyone | 2 |
To be approved by Majority | 3 |
To be approved by First Responder | 4 |
Status | Value |
---|---|
Requested | 0 |
Approved | 1 |
Rejected | 2 |
Cancelled | 3 |
Request Approval For A Service Request
Send a Service Request for approval
Note: "email_content" is an optional parameter for sending approval. If not provided, the default approval notification will be sent to approvers.
1 | curl -v -u api_key:X -H "Content-Type: application/json" -d '{"approver_id":39479, "approval_type": 2,"email_content": "Your approval email body goes here."}' -X POST 'https://domain.freshservice.com/api/v2/tickets/20/approvals' |
List All Ticket Approvals
Retrieve all approvals on a Service Request with the given ID from Freshservice.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/20/approvals' |
View An Approval
Retrieve an approval on a Service Request with the given ID from Freshservice
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/20/approvals/1' |
Cancel An approval
Cancel an existing approval on a Service Request
Note: You can only update the approval status of a request to "cancelled" state through this API. Any other status change will be done based on the approver's action.
1 | curl -v -u api_key:X -H "Content-Type: application/json" -d '{ "approval_status":{ "id":3 }}' -X PUT 'https://domain.freshservice.com/api/v2/tickets/20/approvals/1' |
Send Reminder For An Approval
Resends a reminder for a specific Approval raised for the ticket
1 | curl -v -u api_key:X -H "Content-Type: application/json" -d '' -X PUT 'https://domain.freshservice.com/api/v2/tickets/20/approvals/1/remind' |
Tasks
This section lists all API that can be used to create, edit or otherwise manipulate Ticket Tasks.
Attribute | Type | Description |
---|---|---|
id | number | Unique ID of the task. |
agent_id | number | Id of the agent to whom the task is assigned |
status | number | Status of the task, 1-Open, 2-In Progress, 3-Completed |
due_date | DateTime | Due date of the task |
notify_before | number | Time in seconds before which notification is sent prior to due date |
title | string | Title of the task |
description | string | Description of the task |
created_at | DateTime | Timestamp at which the task was created |
updated_at | DateTime | Timestamp at which the task was updated |
closed_at | DateTime | Timestamp at which the task was closed |
group_id | number | Unique ID of the group to which the task is assigned |
Create a Task
Create a new task on a ticket request in freshservice
Attribute | Type | Description |
---|---|---|
workspace_id | number | ID of the workspace to which the task belongs. This attribute is applicable only to accounts on the Employee Support Mode. The default value is the ID of the workspace of the ticket. |
agent_id | number | ID of the agent to whom the task is assigned |
status | number | Status of the task, 1-Open, 2-In Progress, 3-Completed |
due_date | datetime | Due date of the task |
notify_before | number | Time in seconds before which notification is sent prior to due date |
title | string | Title of the task |
description | string | Description of the task |
group_id | number | Unique ID of the group to which the task is assigned |
1 2 3 4 5 6 7 | curl -v -u api_key:X -H "Content-Type: application/json" -d '{ "due_date": "2020-04-03T10:26:13.067Z", "notify_before": 0, "title": "Supply lightsabers to all the Jedis", "description": "We need to re-supply to win the war!", "workspace_id": 3 }' -X POST 'https://domain.freshservice.com/api/v2/tickets/1/tasks' |
View a Task
Retrieve a task on a Ticket with the given ID from Freshservice
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X GET 'https://domain.freshservice.com/api/v2/tickets/1/tasks/1' |
View all Tasks
Retrieve the tasks on a Ticket with the given ID from Freshservice.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/1/tasks' |
Update a Task
Update an existing task on an existing Ticket in Freshservice
1 2 3 4 5 6 7 | curl -v -u api_key:X -H "Content-Type: application/json" -X PUT -d '{ "status": 3, "notify_before": 0, "title": "Supply lightsabers to all the Jedis", "description": "We need to re-supply to win the war!", "workspace_id": 2 }' 'https://domain.freshservice.com/api/v2/tickets/1/tasks/1' |
Delete a Task
Delete the task on a Ticket with the given ID from Freshservice
Note: Deleted tasks are permanently lost. You can't retrieve them once it's get deleted.
1 | curl -v -u api_key:X -X DELETE 'https://domain.freshservice.com/api/v2/tickets/1/tasks/1' |
CSAT
This section lists all API that can be used to view Ticket CSAT Response.
Attribute | Type | Description |
---|---|---|
id | number | Unique ID of the survey response. |
overall_rating_text | string | Overall feedback text of the survey response |
overall_rating | number | Feedback code of the survey response |
primary_question | string | Primary survey question |
questionnaire_responses | array of hashes | Contains the list of responded questions and answer(s) chosen.
|
created_at | DateTime | Timestamp at which the survey response was created |
updated_at | DateTime | Timestamp at which the survey response was updated |
CSAT Response
Retrieve a csat response of a Ticket with the given ID from Freshservice
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X GET 'https://domain.freshservice.com/api/v2/tickets/1/csat_response' |
Conversations
Conversations consist of replies as well as public and private notes added to a ticket. Notes are non-invasive ways of sharing updates about a ticket amongst agents and requesters. Private notes are for collaboration between agents and are not visible to the requester. Public notes are visible to, and can be created by, both requesters and agents.
Attribute | Type | Description |
---|---|---|
attachments | array of attachment objects | Attachments associated with the conversation. The total size of all of a ticket's attachments cannot exceed 40 MB. |
body | string | Content of the conversation in HTML |
body_text | string | Content of the conversation in plain text |
id | number | ID of the conversation |
incoming | boolean | Set to true if a particular conversation should appear as being created from the outside (i.e., not through the web portal) |
to_emails | array of strings | Email addresses of agents/users who need to be notified about this conversation |
private | boolean | Set to true if the note is private |
source | number | Denotes the type of the conversation. |
support_email | string | Email address from which the reply is sent. For notes, this value will be null. |
ticket_id | number | ID of the ticket to which this conversation is being added |
user_id | number | ID of the agent/user who is adding the conversation |
created_at | datetime | Conversation creation timestamp |
updated_at | datetime | Conversation updated timestamp |
Conversation Properties
Conversations use certain fixed numerical values to denote their source. These numerical values along with their meanings are given below.
Note : This source attribute will be returned in the response body of the List All Conversations of a Ticket and View a ticket (only when 'include=conversation' is passed in url) endpoints.
Source Type | Value |
---|---|
0 | |
form | 1 |
note | 2 |
status | 3 |
meta | 4 |
feedback | 5 |
forward_email | 6 |
Create a Reply
Attribute | Type | Description |
---|---|---|
body * | string | Content of the note in HTML format |
attachments | array of attachment objects | Attachments. The total size of all the ticket's attachments (not just this note) cannot exceed 40 MB. |
from_email | string | The email address from which the reply is sent. By default the global support email will be used. |
user_id | number | ID of the agent/user who is adding the note |
cc_emails | array of strings | Email address added in the 'cc' field of the outgoing ticket email. |
bcc_emails | array of strings | Email address added in the 'bcc' field of the outgoing ticket email. |
* Mandatory attribute |
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X POST -d '{ "body":"We are working on this issue. Will keep you posted." }''https://domain.freshservice.com/api/v2/tickets/141/reply' |
Reply to a Ticket With Attachments
Note:
1. This API request must have its Content-Type set to multipart/form-data.
2. For more information on attachment refer to this section.
1 | curl -v -u api_key:X -F 'attachments[]=@/Users/user/Desktop/api2.png' -F 'body=We are working on this issue. Will keep you posted.' -X POST 'https://domain.freshservice.com/api/v2/tickets/51/reply' |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 | { "conversation": { "id": 4289865, "user_id": 1232463344, "from_email": "user@yourcompany.com", "cc_emails": [], "bcc_emails": [], "body": "<div>We are working on this issue. Will keep you posted.</div>", "body_text": "We are working on this issue. Will keep you posted.", "ticket_id": 51, "to_emails": [ "tom@outerspace.com" ], "attachments": [ { "id": 368557, "content_type": "image/png", "size": 274688, "name": "api2.png", "attachment_url": "https://s3.amazonaws.com/cdn.freshgenie.com/data/helpdesk/attachments/production/19852343/original/api2.png", "created_at": "2021-04-12T07:41:03Z", "updated_at": "2021-04-12T07:41:04Z" } ], "created_at": "2021-04-12T07:41:04Z", "updated_at": "2021-04-12T07:41:04Z" } } |
Create a Note
Note: By default, any note that you add will be private. If you wish to add a public note, set the parameter to false.
Attribute | Type | Description |
---|---|---|
attachments | array of attachment objects | Attachments. The total size of all the ticket's attachments (not just this note) cannot exceed 40 MB. |
body * | string | Content of the note in HTML format |
incoming | boolean | Set to true if a particular note should appear as being created from the outside (i.e., not through the web portal). The default value is false |
notify_emails | array of strings | Email addresses of agents/users who need to be notified about this note |
private | boolean | Set to true if the note is private. The default value is true. |
user_id | number | ID of the agent/user who is adding the note |
* Mandatory attribute |
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X POST -d '{ "body":"Hi tom, Still Angry", "private":false }' 'https://domain.freshservice.com/api/v2/tickets/265/notes' |
Create a Note With Attachment
Note:
1. This API request must have its Content-Type set to multipart/form-data.
1 | curl -v -u api_key:X -F 'attachments[]=@/Users/user/Desktop/api_attach.png' -F 'body=Hi tom, Still Angry' -F 'private=false' -X POST 'https://domain.freshservice.com/api/v2/tickets/51/notes' |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 | { "conversation": { "id": 4289856, "incoming": false, "private": false, "user_id": 1232463344, "support_email": null, "body": "<div>Hi tom, Still Angry</div>", "body_text": "Hi tom, Still Angry", "ticket_id": 51, "to_emails": [], "attachments": [ { "id": 368555, "content_type": "image/png", "size": 115399, "name": "api_attach.png", "attachment_url": "https://s3.amazonaws.com/cdn.freshgenie.com/data/helpdesk/attachments/production/19852343/original/api_attach.png", "created_at: "2021-04-12T06:44:09Z", "updated_at": "2021-04-12T06:44:09Z" } ], "created_at": "2021-04-12T06:44:09Z", "updated_at": "2021-04-12T06:44:09Z" } } |
Update a Conversation
Note:
Only public & private notes can be edited.
Attribute | Type | Description |
---|---|---|
body | string | Content of the note in HTML format |
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X PUT -d '{ "body":"Can you provide some screenshots?" } 'https://domain.freshservice.com/api/v2/conversations/5' |
Update a conversation With Attachment
Note:
1. This API request must have its Content-Type set to multipart/form-data.
2. For more information on attachment refer to this section.
1 | curl -v -u api_key:X -F 'attachments[]=@/Users/user/Desktop/api2.png' -F 'body=Can you provide some screenshots?' -X PUT 'https://domain.freshservice.com/api/v2/conversations/4289856' |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 | { "conversation": { "id": 4289856, "incoming": false, "private": false, "user_id": 1232463344, "support_email": null, "body": "Can you provide some screenshots?", "body_text": "Can you provide some screenshots?", "ticket_id": 51, "to_emails": [], "attachments": [ { "id": 368555, "content_type": "image/png", "size": 115399, "name": "api_attach.png", "attachment_url": "https://s3.amazonaws.com/cdn.freshgenie.com/data/helpdesk/attachments/production/19852343/original/api_attach.png", "created_at": "2021-04-12T06:44:09Z", "updated_at": "2021-04-12T06:44:09Z" }, { "id": 368556, "content_type": "image/png", "size": 274688, "name": "api2.png", "attachment_url": "https://s3.amazonaws.com/cdn.freshgenie.com/data/helpdesk/attachments/production/19852343/original/api2.png", "created_at": "2021-04-12T06:48:53Z", "updated_at": "2021-04-12T06:48:53Z" } ], "created_at": "2021-04-12T06:44:09Z", "updated_at": "2021-04-12T06:48:53Z" } } |
Delete a Conversation
1 | curl -v -u api_key:X -X DELETE 'https://domain.freshservice.com/api/v2/conversations/5' |
Delete a Conversation Attachment
This API helps you delete an attachment from a conversation.
1 | curl -v -u api_key:X -X DELETE 'https://domain.freshservice.com/api/v2/conversations/1/attachments/1' |
List All Conversations of a Ticket
This API helps you List All Conversations of a Ticket.
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X GET 'https://domain.freshservice.com/api/v2/tickets/20/conversations' |
1. This ticket's conversation has more than 30 entries. This request returns the second page (entries from 31 to 60).
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/tickets/1/conversations?page=2' |
Problems
This section lists all API that can be used to create, edit or otherwise manipulate Problem.
Attribute | Type | Description |
---|---|---|
id | number | Unique identifier of the Problem Read-Only |
workspace_id | number | ID of the workspace that the problem belongs to. If not provided, the ID of the primary workspace will be defaulted. Applicable only to accounts on the Employee Support Mode. |
agent_id | number | Unique identifier of the agent to whom the Problem is assigned |
requester_id * | number | Unique identifier of the initiator of the problem. Mandatory |
group_id | number | Unique identifier of the agent group to which the Problem is assigned |
description * | string | HTML content of the problem. Description and description_html should not be passed together Mandatory |
description_text | string | Plain text content of the problem Read-Only |
priority * | number | Priority of the Problem 1-Low, 2-Medium, 3-High, 4-Urgent |
status * | number | Status identifier of the Problem. 1-Open, 2-Change Requested, 3-Closed Mandatory |
impact * | number | Impact of the Problem. 1-Low, 2-Medium, 3-High Mandatory |
known_error | boolean | States that the problem is known issue or not. true or false |
subject * | string | Subject of the Problem Mandatory |
due_by * | DateTime | Timestamp at which Problem due ends Mandatory |
department_id | number | Unique ID of the department initiating the Problem |
category | string | Category of the Problem |
sub_category | string | Sub-category of the Problem |
item_category | string | Item of the Problem |
created_at | DateTime | Timestamp at which Problem was created |
updated_at | DateTime | Timestamp at which Problem was last updated |
associated_change | number | Unique ID of the Change associated with the Problem Read-Only |
custom_fields | Hash | Key value pairs containing the names and values of custom fields. |
analysis_fields | Hash | Key value pairs containing the names and values of Problem Cause, Problem Symptom and Problem Impact |
assets | hash | List of assets associated with the problem |
Create a Problem
Create a new problem request in Freshservice
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 | curl -v -u api_key:X -H "Content-Type: application/json" -d ' { "subject": "Unable to reach email server", "email": "sample@freshservice.com", "description": "<div>Hi guys, <br/><br/>We have been facing issues when we try to reach Email Server 3. Looks like there is something wrong here.<br/><br/>Regards<br/> Rachel<br/> </div>", "due_by": "2020-07-20T16:18:46Z", "priority": 2, "status": 2, "impact": 1, "category": "Hardware", "sub_category": "Peripherals", "item_category": "Router", "agent_id": 1, "group_id": 1, "department_id": 1, "custom_fields": { "sample_text_field": "Sample Text" }, "analysis_fields": { "problem_cause": { "description": "Problem cause description" }, "problem_symptom": { "description": "Problem symptom description" }, "problem_impact": { "description": "Problem impact description" } }, "workspace_id": 3 } ' -X POST 'https://domain.freshservice.com/api/v2/problems' |
Create Problem with attachment
Note:
1. This API request must have its Content-Type set to multipart/form-data.
2. For more information on attachment refer to this section.
1 | curl -v -u api_key:X -F 'subject=Unable to reach email server' -F 'description=Hi guys, We have been facing issues when we try to reach Email Server 3. Looks like there is something wrong here.' -F 'priority=2' -F 'status=2' -F 'impact=1' -F 'due_by=2021-04-21T16:18:46Z' -F 'email=user@yourcompany.coom' -F 'attachments[]=@/Users/user/Desktop/api_attach.png' -F 'workspace_id=3' -X POST 'https://domain.freshservice.com/api/v2/problems' |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 | { "problem": { "id": 47, "agent_id": null, "description": "<div>Hi guys, We have been facing issues when we try to reach Email Server 3. Looks like there is something wrong here.</div>", "description_text": "Hi guys, We have been facing issues when we try to reach Email Server 3. Looks like there is something wrong here.", "requester_id": 1232463344, "subject": "Unable to reach email server", "group_id": null, "priority": 2, "impact": 1, "status": 2, "due_by": "2021-04-21T16:18:46Z", "known_error": false, "department_id": null, "category": null, "sub_category": null, "item_category": null, "created_at": "2021-04-12T11:22:54Z", "updated_at": "2021-04-12T11:22:54Z", "workspace_id": 3, "associated_change": null, "assets": [] "custom_fields": { "requester": null, "subject": null, "description": null, "status": null, "priority": null, "impact": null, "due_by": null, "group": null, "agent": null, "department": null, "category": null }, "analysis_fields": {} } } |
Create Problem with assets
Note:
"assets" key: contains comma (,) separated hash of the assets, each with key display id.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 | curl -v -u api_key:X -H "Content-Type: application/json" -d ' { "subject": "Unable to reach email server", "email": "sample@freshservice.com", "description": "<div>Hi guys, <br/><br/>We have been facing issues when we try to reach Email Server 3. Looks like there is something wrong here.<br/><br/>Regards<br/> Rachel<br/> </div>", "due_by": "2020-07-20T16:18:46Z", "priority": 2, "status": 2, "impact": 1, "category": "Hardware", "sub_category": "Peripherals", "item_category": "Router", "agent_id": 1, "group_id": 1, "department_id": 1, "workspace_id": 2, "custom_fields": { "sample_text_field": "Sample Text" }, "analysis_fields": { "problem_cause": { "description": "Problem cause description" }, "problem_symptom": { "description": "Problem symptom description" }, "problem_impact": { "description": "Problem impact description" } }, "assets": [ { "display_id": 8 }, { "display_id": 9 } ] } ' -X POST 'https://domain.freshservice.com/api/v2/problems' |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 | { "problem": { "id": 1, "agent_id": null, "requester_id": 1, "description": "<div>Hi guys, <br/><br/>We have been facing issues when we try to reach Email Server 3. Looks like there is something wrong here.<br/><br/>Regards<br/> Rachel<br/> </div> ", "description_text": "Hi guys, We have been facing issues when we try to reach Email Server 3. Looks like there is something wrong here. Regards Rachel", "due_by": "2020-07-20T16:18:46Z", "subject": "Unable to reach email server", "group_id": null, "priority": 2, "impact": 1, "status": 2, "known_error": false, "department_id": null, "category": "Hardware", "sub_category": "Peripherals", "item_category": "Router", "created_at": "2020-02-04T05:50:57Z", "updated_at": "2020-02-04T05:50:57Z", "workspace_id": 3, "associated_change": 1, "custom_fields": { "sample_text_field": "Sample Text" }, "analysis_fields": { "problem_cause": { "description": "<div> Problem cause description </div>", "description_text": "Problem cause description" }, "problem_symptom": { "description": "<div> Problem symptom description </div>", "description_text": "Problem symptom description" }, "problem_impact": { "description": "<div> Problem impact description </div>", "description_text": "Problem impact description" } }, "assets": [ { "name": "Dell Monitor", "description": null, "ci_type_id": 12, "impact": 1, "created": "2019-12-13T12:31:47+05:30", "updated": "2019-12-13T12:31:47+05:30", "user_id": null, "department_id": null, "assigned_on": null, "agent_id": null, "author_id": 2, "author_type": "User", "deleted": false, "display_id": 8, "salvage": null }, { "name": "Logitech Mouse", "description": null, "ci_type_id": 4, "impact": 1, "created": "2019-12-13T12:31:47+05:30", "updated": "2019-12-13T12:31:47+05:30", "user_id": null, "department_id": null, "assigned_on": null, "agent_id": null, "author_id": 2, "author_type": "User", "deleted": false, "display_id": 9, "salvage": null } ] } } |
View a Problem
Retrieve the problem with the given ID from Freshservice
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X GET 'https://domain.freshservice.com//api/v2/problems/1' |
View List of Problems
Retrieve a list of all Problems in Freshservice
Note:
If a workspace_id is not specified as a URL parameter, only problems from the primary workspace will be included in the response. If workspace_id is specified as 0, problems from across all workspaces will be included in the response with just the global fields. Applicable only to accounts on the Employee Support Mode.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/problems' |
1. Get the list of all problems from workspaces to which the user has access.
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/problems?workspace_id=0' |
2. Get the list of problems from a specific workspace
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/problems?workspace_id=3' |
Update a Problem
Update an existing Problem in Freshservice
Note:
The workspace_id attribute cannot be updated through the Update operation. It can only be updated through the Move operation.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 | curl -v -u api_key:X -H "Content-Type: application/json" -X PUT -d '{ "subject": "Unable to reach email server", "email": "sample@freshservice.com", "description": "<div>Hi guys, <br/><br/>We have been facing issues when we try to reach Email Server 3. Looks like there is something wrong here.<br/><br/>Regards<br/> Rachel<br/> </div>", "due_by": "2020-07-20T16:18:46Z", "priority": 2, "status": 3, "impact": 2, "category": "Hardware", "sub_category": "Peripherals", "item_category": "Router", "agent_id": 1, "group_id": 1, "department_id": 1, "custom_fields": { "sample_text_field": "Sample Text" }, "analysis_fields": { "problem_cause": { "description": "Problem cause description" }, "problem_symptom": { "description": "Problem symptom description" }, "problem_impact": { "description": "Problem impact description" } } }' 'https://domain.freshservice.com/api/v2/problems/1' |
Update Problem with attachment
Note:
1. This API request must have its Content-Type set to multipart/form-data.
2. For more information on attachment refer to this section.
1 | curl -v -u api_key:X -F 'subject=Unable to reach email server' -F 'description=Hi guys, We have been facing issues when we try to reach Email Server 3. Looks like there is something wrong here.' -F 'priority=2' -F 'status=2' -F 'impact=1' -F 'due_by=2021-04-21T16:18:46Z' -F 'email=fuser@yourcompany.com' -F 'attachments[]=@/Users/user/Desktop/api2.png' -X PUT 'https://domain.freshservice.com/api/v2/problems/47' |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 | { "problem": { "id": 47, "agent_id": null, "description": "Hi guys, We have been facing issues when we try to reach Email Server 3. Looks like there is something wrong here.", "description_text": "Hi guys, We have been facing issues when we try to reach Email Server 3. Looks like there is something wrong here.", "requester_id": 1232463344, "subject": "Unable to reach email server", "group_id": null, "priority": 2, "impact": 1, "status": 2, "due_by": "2021-04-21T16:18:46Z", "known_error": false, "department_id": null, "category": null, "sub_category": null, "item_category": null, "created_at": "2021-04-12T11:22:54Z", "updated_at": "2021-04-12T11:22:54Z", "workspace_id": 3, "assets": [], "associated_change": null, "custom_fields": { "requester": null, "subject": null, "description": null, "status": null, "priority": null, "impact": null, "due_by": null, "group": null, "agent": null, "department": null, "category": null }, "analysis_fields": {} } } |
Move a Problem
This API moves a problem to a different workspace, while also allowing the assigned group and agent to be modified.
Note:
This endpoint is applicable only to accounts on the Employee Support Mode.
1 | curl -v -u api_key:X -X PUT -d '{ "workspace_id": 3, "group_id": 3, "owner_id": 4 }' 'https://domain.freshservice.com/api/v2/problems/1/move_workspace' |
Delete a Problem
Delete the Problem with the given ID from Freshservice
1 | curl -v -u api_key:X -X DELETE 'https://domain.freshservice.com/api/v2/problems/1' |
Restore a Problem
The API mentioned previously. If you deleted some problems and regret doing so now, this API will help you restore them.
1 | curl -v -u api_key:X -H "Content-Type: application/json" -X PUT -d '' 'https://domain.freshservice.com/api/v2/problems/1/restore' |
List All Problem Fields
Retrieve all the Fields that constitute the Problem Object
Note:
By default, only global fields and fields from the primary workspace will be returned for accounts on the Employee Support Mode. For fields from other workspaces, use the workspace_id filter.
Problem field | Description |
---|---|
id | Unique ID of the Field |
workspace_id | ID of the workspace to which this problem field belongs. This attribute is applicable only to accounts on the Employee Support Mode. |
created_at | Date time at which the field was added |
updated_at | Date time at which the field was modified |
name | Name of the field |
label | Label of the field for display |
description | Description of the field |
field_type | Indicates if the field is a checkbox, dropdown, text field |
required | True if the field is marked mandatory |
required_for_closure | True if the field is marked mandatory while closing the problem item |
default_field | True if the field is a default field. False if customm |
choices | List of values supported by the field |
nested_fields | contain details of nested fields |
1 | curl -v -u api_key:X -X GET 'https://domain.freshservice.com/api/v2/problem_form_fields' |