1. Click the Business Settings menu.
2. Click the Payroll Settings submenu.
3. Click the Web Hooks button.
4. Click the Add button.
   
5. Complete the following fields:
   • Description.
   • URL.
   • Events.
6. Click the Save button.
   

1. Click the Business Settings menu.
2. Click the Payroll Settings submenu.
3. Click the Web Hooks button.
4. Select ‌the Enable clock in/clock out web hooks tick box.
   

1. Click the Business Settings menu.
2. Click the Payroll Settings submenu.
3. Click the Web Hooks button.
4. Click the Test button.
   
5. Select the required event and click the Test Web Hook button.
   

1. Click the Business Settings menu.
2. Click the Payroll Settings submenu.
3. Click the Web Hooks button.
4. Click on the Webhook that needs editing.
   
5. Make the required changes and click the Save button.
   

1. Click the Business Settings menu.
2. Click the Payroll Settings submenu.
3. Click the Web Hooks button.
4. Click the Delete button.
   
5. Click the Ok button.
   

The Web Hook events with message data types sent that are currently available are:

• Employee Created (NzUnstructuredEmployeeModel)
• Employee Terminated (NzUnstructuredEmployeeModel)
• Employee Updated (NzUnstructuredEmployeeModel)
• Pay-Run Finalised (FinalisePayRunOptions)
• Pay Run Deleted (pay run ID)
• Pay-Run Initialised (PayRunModel) 
• Bank Account Deleted (bank account ID)
• Bank Account Updated (NzBankAccountModel)
• Employee Recurring Deduction Deleted (deduction ID)
• Employee Deduction Updated (NzEmployeeRecurringDeductionModel)
• Leave Request Approved (UnitLeaveRequestResponseModel)
• Leave Request Created (NzUnitLeaveRequestModel)
• Leave Request Deleted (UnitLeaveRequestResponseModel)
• Leave Request Declined (UnitLeaveRequestResponseModel)
• Leave Request Updated (NzUnitLeaveRequestModel)

Data is sent inside a wrapper class (Microsoft.AspNet.WebHooks.WebHookWorkItem), with the relevant data inside the Notification array.

If the call to the web hook URL does not return a success result, for example a HTTP 200 or HTTP 201, we will retry the sync at increasingly higher delays.

• First attempt: Immediate.
• Retry 1: 1 minute after first attempt.
• Retry 2: 2 minutes after previous retry.
• Retry 3: 4 minutes after previous retry.
• Retry 4: 8 minutes after previous retry.
• Retry 5: 15 minutes after previous retry.
• Retry 6: 30 minutes after previous retry.
• Retry 7: 1 hour after previous retry.

If the web hook attempt is not successful after seven retries, we will not re-attempt the sync.

We include Web Hook message verification with each web hook registration by computing a sha256 hash of the message payload using HMAC and web hook secret. Each event will contain the hashed value within the header response MS-Signature. You can use an application like https://www.freeformatter.com/hmac-generator.html to test the resulting hash.

Please note the hash is sensitive to any whitespace in the request content. It is recommended that you read the content as a string without any formatting, then pass it through an HMAC hash generator library along with your secret.