FrontSpin Webhooks
Webhooks API
Table of Contents
Using Webhooks
After setting up a webhook with its URL and a specific trigger, the application will send notifications whenever the defined trigger action is executed. To prevent unnecessary retries or the notification from being marked as failed, your application must respond with a 2XX status code.
FrontSpin waits for the response for about 10 minutes. After that, it’s considered a time-out.
Each webhook notification sent includes the x-frontspin-signature header, which contains an HMAC-SHA256 signature generated using your webhook_secret value and the payload body associated with your webhook.
Retries
If a 2XX response isn’t received or the request times out after waiting for 10 minutes, the application will retry up to four times, at random intervals between 1 and 5 minutes.
After 4 retries, that webhook notification will be marked as failed.
The number of attempts is reflected in the webhook body under the deliveryAttempts property.
Triggers
Currently supported triggers:
Contacts - contact.create - contact.update - contact.delete - contact.bulk.create - contact.bulk.update
Leads - lead.create - lead.update - lead.delete - lead.bulk.create - lead.bulk.update
Accounts - account.create - account.update
Calls - call.create - call.update
Lists - list.lead.bulk.update - list.contact.bulk.update
Call Transcript - call.ai.update
Please remember to process the webhook payload asynchronously and respond with a 2XX as quickly as possible.
Example
If the action is successful, the webhook content will contain the whole object data.
Contact
Single Delete
Bulk Update
Lead
Bulk Update
Account
Call
* When parsing the call.create message, it may, depending on timing, include call.update fields. In this case, you won’t receive a separate call.update notification because the message content was already sent
Single create with minimum message data
Single create with call.update message data
Single update
List
Lead Bulk Update 
Contact Bulk Update
Call Transcript
