For the GET query i use: https://webservices4.autotask.net/atservicesrest/v1.0/Tickets/query?search={"filter": [{"op": "eq","field": "ticketNumber","value": "T20210309.0001"}]}. ChangeInfoFields are available regardless of whether they are Active or Inactive. You can make this a default setting. The Autotask REST API Easily create an Autotask survey Easy copy/paste process takes less than 5 minutes Including survey in existing notifications means no extra emails for your clients Sync Autotask ticket details with feedback Gain further context about feedback by retrieving ticket info through the Autotask API. This entity describes an Autotask SubscriptionPeriod. A Subscription creates recurring billing items for Assets when there is no need to track labor costs against subscription revenue; for example, when billing in installments. The New and Edit pages for each entity feature a notification panel that is accessed from a persistent handle at the bottom of the page. This entity describes a ticket category applied to tickets in Autotask to specify features and fields that appear on the ticket detail. The function of this entity is to describe the number of units of a specific service with an association to a Recurring Service contract for a specific date range. This entity contains attachments for the Projects entity. Thanks for your feedback. Some entities support file attachments. Configure automatic ticket creation for Workplace Manager - Datto } The client can access and act on the entity's field parameters: supplying, updating, or deleting the field data. window.open(uri); For example, when updating an entity, you may not be able to update all fields within the entity. This entity's purpose is to describe a list item associated with a UserDefinedFieldDefinition entity that has dataType = List. In addition, a stumbling block I noted was to double check the AssignedResourceID has the actual role assigned via AssignedResourceRoleID. A Contract Rate is associated with a Role and is specific to a contract. https://webservices4.autotask.net/atservicesrest/v1.0/Tickets. Create a Ticket in Autotask using Powershell Making IT work The Status defaults to the current status of the parent entity when the page or dialog box is opened. Read-Only:Read-Only fields cannot be changed by, Required: Required fields must be present when you attempt a. They can click New Ticket on the Autotask interface sub-navigation menu to open the New Ticket window. The id value is set by the system and cannot be changed by the user; for example, if you attempt to specify a value for the id field when using the POSTAPI call, the create will fail. TicketType must = Incident before the ticket can be associated with a ProblemTicketID. Saves and closes the note or time entry and opens the Forward/Modify Ticket(s) page. Ticket - Autotask Tickets with no TicketType specified are set automatically to Service Request. via the API and attached to the OnPlus Service Desk queue. The current data is loaded when the section is first expanded. Available in the UI only when the installed module is enabled. 5. The function of this entity is to describe the associations between Change Request tickets and both Incidents and Problems. Do not confuse it with Currency local term selection, which is not available when using Multi-currency. UPDATE: I have published an updated version of this article based on our new PowerShell module for Autotask. Visit our SOAPAPIlifecycle FAQ article to learn more. This entity contains the attachments for the ConfigurationItemNotes entity. var uri = 'https://docs.google.com/forms/d/e/1FAIpQLSdw1y-_z7_O1tSWNFkiDliribqAz5IrqAiJJ6u2KsbEvICTqw/viewform?usp=pp_url&entry.876121135=' + document.location.href; This entity describes an Autotask Contract Block which represents a block of hours purchased for a Block Hour type Contract. Some resources contain additional objects in child collections; these resources have an additional Child collection access URLs field in their Online Help articles. For more information about fields marked as picklists, review our Understanding picklists article. Thanks for your feedback. To retrieve more detailed information specific to a particular Autotask implementation, use the Web Services API call. They can click New Ticket on the Autotask interface sub-navigation menu to open the New Ticket window. Visit our SOAP API lifecycle FAQ article to learn more. This entity represents company (account)categories in Autotask. Create Ticket Note. Visit the Ideas forum! This entity describes an Autotask Inventory location, that is, a physical or virtual place where your company stores or assigns inventory items. This entity represents aliases for ticket and article tags in Autotask. This entity's purpose is to describe a predecessor/successor arrangement between two project schedule items. The properties represent data fields. When a SubIssueType value is provided, the associated IssueType value must also be provided. If it is selected, you can update the status of all incidents. According to their documentation it requires the URI https://webservices4.autotask.net/atservicesrest/v1.0/Tickets and then the body contains the JSON formatted data: But this doesn't seem to work either and Datto are taking forever to respond to support tickets these days. The ArticlePlainTextContent entity contains the plain text version of body content held by a Knowledgebase article. We're using Power Apps to capture information and then Flow passes it to Autotask, i can pull information using GET but unable to create anything. This entity describes notes created by an Autotask user and associated with a Task entity. Head on over to our Community Forum! Visit our SOAPAPIlifecycle FAQ article to learn more. On the incidents, the Internal Notes are created as a reply to the Summary Notes. This entity describes an Autotask Ticket. If TicketType = Problem and incidents are associated with the ticket, TicketType cannot be changed to Incident or Service Request until the incidents are disassociated from the ticket. It determines a customer's total taxes on billing items. The check boxes are shortcuts to manually selecting or clearing role-based recipients on the Notification panel. The allowed actions are specific to the object. This entity describes an Autotask Time Entry. This entity manages the tags associated with tickets in Autotask. Provide feedback for the Documentation team. The RMA ticket category cannot be edited through the API. Resources receive assignment to one or more roles through their department and queue associations. This entity enables you to increase inventory counts associated with the InventoryProducts entity. This entity's purpose is to describe a group of Service entity items that are priced and billed as one component of Recurring Service type contract. ConfigurationItemWebhookExcludedResources. Enter your API credentials and then click Connect. You can only create it; you cannot query or update it. 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 . A Resource + Role combination assigned to a ticket must be associated with at least one Service Desk Queue. function SendLinkByMail(href) { AllocationCodeID is required on create() and update() if your company has enabled the Autotask system setting that requires a Work Type on a Ticket. Visit the Ideas forum! It must have an association with an Autotask Opportunity entity, and it allows users to specify and track multiple products, services, labor items, etc., that further define the Opportunity. window.open(uri); A project defines and organizes a group of related tasks, events, and documents. This entity represents a document in Autotask. This entity describes detailed information about on-hand. This entity contains the attachments for the. This entity's purpose is to describe an asset category. Does ZnSO4 + H2 at high pressure reverses to Zn + H2SO4? For example, 'T20200615.0674.'. Each entity type object contains an array of properties that describe instances of the entity type. Write. Access deactivation for version 1.5 began in Q1 2022 and will enter its concluding phases in October 2022. update() is allowed on a Ticket with an inactive ContactID value if that value is not being changed, or if a new active value is assigned. This object describes Autotask Assets (previously known as Configuration Items), other than the primary Assets (Ticket.configurationItemID). This entity contains the attachments for the ProjectNotes entity. If there is no Asset SLA, then check the Contract Service or Bundle SLA. If a ticket is created with the 'RMA' ticket category via the API and no value is supplied for this field, the ticket category default value for the field will be used. This entity enables you to decrease inventory counts associated with the InventoryProducts entity. If a value is not provided for ChangeApprovalType: For the ContactID field, Contact.AccountID must = Ticket.AccountID or the ParentAccountID of Ticket.AccountID. All users can view attachments they uploaded. The following results have been performed on the sandbox of Autotask, to which I have a RTT of about 150-180MS. This entity describes an Autotask Project. GitHub - KelvinTegelaar/AutotaskAPI: Autotask 2020.2 REST API Assets are products that are associated with a Company entity. You can configure API Only security levels to allow the impersonation of other resources on supported endpoints. If you close without saving, the attachments will not be uploaded or attached to the parent entity. Have an idea for a new feature? REST API: User-defined fields (UDFs) - Autotask Hello, i've been trying to create a ticket in Autotask using the API but the documentation (as everyone has already mentioned) is virtually useless. What is a word for the arcane equivalent of a monastery? Click Get current values to update field values. /*