<EntityName>Webhooks (REST API)

This field contains a separate URL that the API calls when the webhook (not the entity) is deleted or inactivated. This call will happen when the resource who created the webhook becomes deleted or deactivated.

The data contained in this field is the webhook configuration ID. Webhooks receive an ID that is unique for the database and each entity.

EXAMPLE  The first webhook you create for the Account entity has ID = 1. Numbering is sequential.

You can create webhooks with an Active setting of True or False. No callouts will occur if a webhook is inactive.

This field is a read-only value that is set to true when the webhook is completely set up.

The condition is true if this webhook triggers as the result of an entity's creation. The condition is blank or false if this webhook does not trigger as the result of an entity's creation.

True if this webhook is triggered by an entity being deleted. Blank or false if this webhook is not triggered by an entity being deleted.

The condition is true if this webhook triggers as the result of entity fields updating. The condition is blank or false if the webhook does not trigger as the result of an entity's fields updating.

This field holds the name of the webhook. The name will appear in the subject line of error and notification emails. A best practice is to use a name that includes the integration name, the entity name and the event that will trigger the callout.

EXAMPLE  Marketo.Contact.Update

This value is an email address that receives notification of any error or alert, in addition to the email address associated with the API user authentication credentials.

This value is the Autotask resource ID of the API user. It is automatically tracked with the callout.

• Each callout owner can only access and manage their own callouts in the API. The intent is to let an integration vendor create and manage their own callouts and not see any other callouts they don’t own.
• Any notifications that go to the callout notification email address are also copied to the callout owner.
• Callouts will continue to execute while the owner is locked out or a password is expired.
• If the callout owner's user account is inactivated, all callouts owned by that username deactivate with a callout to the Deactivation URL.

The recipient of the webhook call needs to confirm the legitimacy and integrity of the callout. You can do so by using a secret key known to both the sender and the recipient. Any combination of letters, number and symbols will work. We recommend a strong key with at least 10 digits.

Refer to Secret key and payload verification.

You can chose to received notification when the Webhook callout requests per hour per entity threshold has been exceeded.

Threshold exceeded is not an error condition, but it can deliver a warning if this callout flag's status is True and a notification email address is available to the callout.

• A notification email would transmit once delivery is delayed, and again when callouts are caught up. The initial message will include the time delay.
• The API will only send the second email if the first one was sent.

GUID stands for Globally Unique Identifier. The value is a webhook ID that is unique across all Autotask databases.