Please enable JavaScript to view this site.

Freshdesk API Data Model Freshdesk Forums

Navigation: Schema: Freshdesk > Tables

tickets_incremental: Freshdesk Tickets (Incremental)

Catalogus: Freshdesk

Schema: Freshdesk

Primaire Sleutels: id

Label: Tickets (Incremental)

Documentatie:

Tickets.

Kan gegevens ophalen en wijzigen met behulp van toevoegen, bijwerken en verwijderen.

Insert Freshdesk-API URL: /tickets

Update Freshdesk-API URL: /tickets

Delete Freshdesk-API URL: /tickets

Veldselectiemethode: NotRequired

Tabelkolommen

De kolommen van de tabel tickets_incremental worden hieronder weergegeven. Elke kolom heeft een SQL-gegevenstype. Voor elke vereiste kolom moet bij het invoegen en bijwerken steeds een nieuwe, niet-lege waarde worden opgegeven.

Naam

Datatype

Label

Verplicht

Documentatie

associated_tickets_count

int64

Associated Tickets Count

☐

 

cf_reference_number

decimal

Reference Number

☐

 

company_id

int64

Company ID

☐

 

created_at

datetime

Created at

☐

Date/time at which the record was created.

deleted

boolean

Deleted

☐

Set as true if the ticket is deleted/trashed. Deleted tickets will not be considered in any views except 'deleted' filter.

description_html

string

Description (HTML)

☐

HTML content of the ticket. Description and description_html should not be passed together.

description_text

string

Description

☐

Plain text content of the ticket.

description

string

Description

☐

 

due_by

datetime

Due by

☐

Ticket due-by time.

email_config_id

int64

Email Configuration ID

☐

ID of email config which is used for this ticket.

email

string

Email

☐

Email address of the requester. If no contact exists with this email address in Freshdesk, it will be added as a new contact.

facebook_id

string

Facebook ID

☐

Facebook ID of the requester. A contact should exist with this facebook_id in Freshdesk.

fr_due_by

datetime

From Due by

☐

Timestamp that denotes when the first response is due.

fr_escalated

boolean

From Escalated

☐

Set to true if the ticket has been escalated as the result of first response time being breached.

group_id

int64

Group ID

☐

ID of Group to which the ticket is assigned.

id

int64

ID

☑

Unique ID of the ticket.

internal_agent_id

int64

Internal Agent ID

☐

 

internal_group_id

int64

Internal Group ID

☐

 

is_escalated

boolean

Is Escalated

☐

Set to true if an escalation was sent.

name

string

Name

☐

Name of the requester.

nr_due_by

datetime

Due by (NR)

☐

 

nr_escalated

boolean

Escalated (NR)

☐

 

phone

string

Phone

☐

Phone number of the requester. If no contact exists with this phone number in Freshdesk, it will be added as a new contact. If the phone number is set and the email address is not, then the name attribute is mandatory.

priority

int16

Priority

☐

Priority of the ticket.

product_id

int64

Product ID

☐

ID of the product to which the ticket is associated.

requester_id

string

Requester ID

☐

User-id of the requester. For existing contacts, requester_id can be passed instead of email.

responder_id

int64

Responder ID

☐

ID of the agent to whom the ticket is assigned.

source

int16

Source

☐

The channel through which the ticket was created.

spam

boolean

Spam

☐

Set as true if the ticket is marked as spam.

status

int16

Status

☐

Status of the ticket.

subject

string

Subject

☐

Ticket subject.

ticket_type

string

Ticket Type

☐

Type property field as defined in ticket fields.

to_emails

string

To Emails

☐

 

twitter_id

string

Twitter ID

☐

Twitter handle of the requester. If no contact exists with this handle in Freshdesk, it will be added as a new contact.

type

string

Type

☐

Helps categorize the ticket according to the different kinds of issues your support team deals with.

updated_at

datetime

Updated at

☐

Date/time at which the record was last updated.

 

10-12-2022 17:06 Versie 22.0.461-PROD+3719

X

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.
  
Disclaimer