Navigation: Catalog: Freshservice > Schemas > Schema: Freshservice > Tables

Tickets: Freshservice Tickets

Catalog: Freshservice

Schema: Freshservice

Primary Keys: id

Label: Tickets

Documentation:

Tickets.

Can retrieve data and change data using insert, update and delete.

Parameters of Table Function

The following parameters can be used to control the behaviour of the table function Tickets. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values.

Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three.

Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third.

Name	Data Type	Required	Default Value	Documentation
email	string	☐		Email address of requester.
filter	string	☐		Pre-defined filter: 'new_and_my_open', 'watching', 'spam' and 'deleted'.
requester_id	int64	☐		ID of requester.
type	string	☐		Type such as 'incident'.
updated_since	datetime	☐	01/01/1900 00:00:00	Limit to tickets updated since.
workspace_id	int64	☐		ID of workspace.

Columns of Table Function

The columns of the table function Tickets are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update.

Name	Data Type	Label	Required	Documentation
business_impact	string	Business impact	☐	Custom field #50000103641 of type custom_paragraph.
call_code	string	Call_code	☐	Custom field #50000011369 of type custom_text.
categorie_aariverside	string	Categorie AaRiverside	☐	Custom field #50000097751 of type nested_field.
categorie_facilitair	string	Categorie Facilitair	☐	Custom field #50000010875 of type nested_field.
categorie_flex	string	Categorie Flex	☐	Custom field #50000010876 of type nested_field.
categorie_nocore_intern	string	Categorie Nocore intern	☐	Custom field #50000099436 of type custom_dropdown.
category	string		☐
created_at	datetime		☐	Date/time at which the record was created.
deleted	boolean		☐	Set as true if the ticket is deleted/trashed. Deleted tickets will not be considered in any views except 'deleted' filter.
department_id	int64		☐
description_text	string		☐	Plain text content of the ticket.
description	string		☐
due_by	datetime		☐	Ticket due-by time.
email_config_id	int64		☐	ID of email config which is used for this ticket.
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 the result of first response time being breached.
group_id	int64		☐	ID of Group to which the ticket is assigned.
id	int64		☑	Unique ID of the ticket.
impacted_locations	string	Impacted locations	☐	Custom field #50000103642 of type custom_text.
incident_alleen_zichtbaar_voor_mij_niet_voor_andere_collegas	boolean	Incident alleen zichtbaar voor mij, niet voor andere collega's	☐	Custom field #50000009057 of type custom_checkbox.
incorrect_ingeladen	string	Incorrect ingeladen	☐	Custom field #50000011765 of type custom_dropdown.
is_escalated	boolean		☐	Set to true if an escalation was sent.
item_category	string		☐
major_incident_type	string	Major incident type	☐	Custom field #50000103640 of type custom_dropdown.
no_of_customers_impacted	string	No. of customers impacted	☐	Custom field #50000103643 of type custom_text.
priority	int16		☐	Priority of the ticket.
requested_for_id	int64		☐
requester_email	string		☐	Email address of the requester.
requester_id	string		☐	User-id of the requester. For existing contacts, requester_id can be passed instead of email.
requester_mobile	string		☐
requester_name	string		☐	Name of the requester.
requester_phone	string		☐	Phone number of the requester.
source	string		☐
spam	boolean		☐	Set as true if the ticket is marked as spam.
stats_agent_responded_at	datetime		☐
stats_assigned_at	datetime		☐
stats_closed_at	datetime		☐
stats_first_assigned_at	datetime		☐
stats_first_resp_time_in_secs	int64		☐
stats_first_responded_at	datetime		☐
stats_group_escalated	boolean		☐
stats_inbound_count	int64		☐
stats_opened_at	datetime		☐
stats_outbound_count	int64		☐
stats_pending_since	datetime		☐
stats_requester_responded_at	datetime		☐
stats_resolution_time_in_secs	int64		☐
stats_resolved_at	datetime		☐
stats_status_updated_at	datetime		☐
status	int16		☐	Status of the ticket.
sub_category	string		☐
subcategorie_facilitair	string	Categorie Facilitair	☐	Nested field #50000010875 level 2 on custom field 'categorie_facilitair'.
subcategorie_flex	string	Categorie Flex	☐	Nested field #50000010876 level 2 on custom field 'categorie_flex'.
subcategorie	string	Categorie AaRiverside	☐	Nested field #50000097751 level 2 on custom field 'categorie_aariverside'.
subject	string		☐	Ticket subject.
subsubcategorie_facilitair	string	Categorie Facilitair	☐	Nested field #50000010875 level 3 on custom field 'categorie_facilitair'.
subsubcategorie_flex	string	Categorie Flex	☐	Nested field #50000010876 level 3 on custom field 'categorie_flex'.
subsubcategorie	string	Categorie AaRiverside	☐	Nested field #50000097751 level 3 on custom field 'categorie_aariverside'.
tasks_dependency_type	int16		☐
type	string		☐	Helps categorize the ticket according to the different kinds of issues your support team deals with.
updated_at	datetime		☐	Date/time at which the record was last updated.
workspace_id	int64		☐

11-12-2024 09:11 Version 24.0.491-PROD+5130

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

Please enable JavaScript to view this site.

Freshservice API Data Model

Tickets: Freshservice Tickets

Parameters of Table Function

Columns of Table Function

Important Safety and Usage Information