TicketAdditionalContacts
This entity describes one or more account contacts assigned to a Ticket, other than the Ticket Contact (Ticket.contactID). Contacts must be associated with the ticket's Company (ticket.companyID). A ticket can have additional contacts even if there is no Ticket Contact.
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: | TicketAdditionalContacts |
Entity Path: |
/atservicesrest/v1.0/TicketAdditionalContacts |
Parent Entity: |
|
Can Create: | |
Can Update: | |
Can Query: | |
Can Delete: | |
Can Have UDFs: |
Conditions and requirements
- A ticket can have no more than 30 additional contacts.
- The same Contact cannot be both the Ticket Contact (Ticket.contactID) and a Ticket Additional Contact.
If an Additional Ticket Contact is specified as the Contact Ticket for the associated Ticket, the Additional Ticket Contact will be removed from the list of additional contacts.
If the associated ticket's Ticket Contact is specified as an Additional Ticket Contact, a message warms that if the contact is added as an Additional Ticket Contact for the associated ticket, the contact will be cleared from the Ticket Contact field.
- A Ticket can have one or more associated Additional Ticket Contacts without having a Ticket Contact.
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:
- The entityInformation REST API call
- Making basic query calls to the REST API
- Advanced query features of the REST API
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 |
---|---|---|---|---|---|
contactID | integer | Contacts | |||
id | long | ||||
ticketID | integer | Tickets |