WebHooks in Engagement Rx provide a powerful mechanism to integrate real-time events with your systems. This document details how to set up and manage WebHooks for your application.

Overview

Engagement Rx WebHooks post events to a client-defined HTTPS endpoint, allowing your applications to respond to events as they occur in real-time. This is useful for syncing data, triggering workflows, or updating your application state in response to user actions on the Engagement Rx platform.

Configuring Your WebHooks

To configure WebHooks, you need to specify the HTTPS endpoint that will receive the WebHook events. This endpoint must be prepared to handle requests according to the following specifications:

• Endpoint URL: The URL must be HTTPS for secure transmission.
• Response Requirement: The endpoint should return an HTTP 204 status code within 5 seconds to acknowledge successful receipt of the event.
• Security: Note that no additional security options are provided; ensure your endpoint is secured appropriately.

See Creating WebHooks on the Data Management page.

Event Delivery

When an event occurs in Engagement Rx, our system will POST a JSON payload to the specified endpoint. The structure of the request model contains a list of PortalEvent objects. For detailed model specifications, refer to PortalEvent Model.

Handling Failures

If the WebHook fails to successfully post the event to your endpoint, the following retry mechanism will be activated:

• Retry Strategy: An exponential backoff approach is employed, retrying the transmission for up to 24 hours.
• Maximum Retry Duration: Retries are attempted over a period of 24 hours from the initial transmission attempt.

Best Practices

• Endpoint Performance: Ensure that your endpoint can handle the expected load and respond within the required 5 seconds.
• Error Handling: Implement robust error handling and logging to troubleshoot and resolve issues that may arise during WebHook processing.
• Security Considerations: As WebHooks will be pushing data to your endpoint, ensure it is secured appropriately to prevent unauthorized access.

Additional Resources

For any further questions or support, please refer to our support portal.