TicketHistory

This entity describes the Ticket History, which tracks changes to the fields of the ticket entity, as well as the fields of any Service Level Agreement associated with the ticket. For the specific actions tracked in the Ticket History entity, refer to View the Ticket History.

IMPORTANT  Note that users with the required permissions can modify SLA event dates in Autotask, but while the original event dates and times no longer appear in the Service Level Agreement grid, an audit trail is added to the Ticket History. Ticket entity fields cannot be edited in the ticket history.

NOTE  You can refer to the Online Help to find root and child access URLs of the entity you wish to query. Refer to Finding resource and child access URLs of REST API entities for more information.

Entity details

Entity Name: TicketHistory

Entity Path:

/atservicesrest/v1.0/TicketHistory
Can Create:  
Can Update:  
Can Query:
Can Delete:  
Can Have UDFs:  

Fields that cannot be queried

The following fields from this entity will return an error when queried.

  • id
  • action
  • detail
  • date
  • resourceID

Conditions and requirements

  • The API TicketHistory entity query requires users to supply and only accepts a single "ticketID equals" filter. Attempting to filter by any other fields or operators will return an error. Attempting to use multiple filters during one query call will also return an error.
  • The API TicketHistory entity will respect the ticket View permissions of the API user. Attempting to query a ticketID that the user does not have access to view will return an error.

Field definitions

The following table describes the standard Autotask fields for this entity. Refer to the following articles for more information about working with these fields:

To learn how to query picklist endpoints, refer to Understanding picklists.

Notes

  • For string datatypes, the number in parentheses ( ) indicates the maximum number of characters allowed.
  • LT indicates Local Term.
  • If this entity has child collections, they will appear in a Child collection access URLs or an Entity URLs and relationships drop-down in the Entity details section of this article.
  • You can call the /query/count/ endpoint of a resource to determine how many records a collection holds.
Field Name Datatype
 Read-Only Is Required Reference Name Picklist
action string (100)    
date datetime    
detail string (1800)    
id long    
resourceID integer Resources  
ticketID integer Tickets  

Additional resources