Retry Failed Webhooks

Description

Current webhooks functionality offers synchronization from Hi Marley to carrier systems (Guidewire etc.). In the event of outage outside of Hi Marley, data in the carrier systems will become out of sync with Hi Marley.

The Retry Webhooks endpoints offers the ability to query for these failed transactions and trigger a retry on the transaction which can be used when the outage is resolved.

 

Hi Marley Postman Documentation

GET Failed Webhook Transactions

POST Retry Webhook Transaction

Overview

The Webhook Retry APIs allow you to:

1. Query failed webhook Posts by start/end time (Unix/UTC), Event ID, and/or Subscription ID
2. Receive a return array of all failed Webhook posts based on search criteria.
3. Use the requestID of the webhook transaction returned to execute POST Retry Webhook API.
4. Once the retry is triggered via the POST: Retry Webhook API, a 'started retry' response will be returned as it is a asynchronous invocation.

Any subsequent retries that are executed will not be seen as a separate webhook POST transaction. The status of the retry with always update the status of the original webhook POST transaction.

Please query based on the time of the original webhook POST transactions since you should see those change to success/not be returned by the query once the retry is successful.

Implementation Recommendation

If your organization has a queuing system implemented to log failed inbound API requests, then the Webhook Retry APIs can be leveraged to implement into your retry/queuing system and reprocess any failed inbound requests.