<EntityName>WebhookFields (REST API)

This article describes the WebhookFields entity of the Autotask REST API. For the SOAP API equivalent of this webhook, refer to <EntityName>WebhookField (SOAP API).

Overview

This entity names a system field that when updated will either trigger a webhook call or is always part of the payload of the webhook. At least one callout field (WebhookField or WebhookUdfField) must be present to make a create or update call.

BEFORE YOU BEGIN  Examples in this article may use the webservices[n].autotask.net placeholder. In such instances, substitute [n] for the zone of your user, as described in Autotask API zones and WSDL versionsFind your zone's API URL for the REST API or Autotask API zones and WSDL versionsFind your zone's WSDL file URL for SOAP API version 1.6.

IMPORTANT  The Autotask GUI uses field labels that can be changed by customer configurations and localization. To ensure consistency for integration programming, the AccountWebhookField and ContactWebhookField entities use REST API field names instead of SOAP API labels. Refer to theSOAP to REST webhook field mapping section of this article to learn how to interpret these names.

Entity details

You can also retrieve this information with the GET and POST REST API calls.

Entity Name: <EntityName>WebhookFields
Can Create:
Can Update:
Can Query:
Can Delete:
Can Have UDFs:  

Fields

Field Name

Label and Description

Datatype Read Only Is Required Reference Name Picklist?

FieldID

integer  

Id

long    

IsDisplayAlwaysField

boolean      

IsSubscribedField

boolean      

WebhookID

integer   <EntityName>Webhook (SOAP API)  

SOAP to REST webhook field mapping

The SOAP AccountWebhookField and ContactWebhookField entities use REST API field names instead of SOAP API labels.

The following table maps webhook-supported SOAP to REST field and label names for the Account/Companies resources, the Contact/Contacts resources, the InstalledProduct/ConfigurationItems resources, the Ticket/Tickets resources, and the TicketNote/TicketNotes resources.

Sample request

Here is a sample REST request that will trigger a callout when the contents of a specific field change.

POST https://webservices[n].autotask.net/atservicesrest/v1.0/CompanyWebhooks/9/Fields

{
"FieldID": "13",
"IsDisplayAlwaysField": true,
"IsSubscribedField": true,
"WebhookID": "9"
}

You must add a separate callout for each field where a change will trigger a callout, or for each field that you want to add to the payload when another field triggers a callout.