Webhooks

quantfolio's webhook functionality is designed to keep external systems updated by notifying them of various events that occur within the deepalpha advisory platform we support a range of event types, such as advice creation, advice completion, and investor updates, among others when one of these events occurs, a webhook is triggered, and a corresponding http request is sent to the specified target url the webhook events provide a way to track and respond to various actions within the system, such as the creation or deletion of advice sessions and investors by handling these events in real time, you can build custom integrations, notifications, or other automated workflows based on the events occurring within the system the webhook functionality supports the following event types related to advice and investor actions these events are triggered when specific actions occur within the system and are sent to the registered webhook url qap investor advice created triggered when a new advice session is created qap investor advice soft deleted triggered when an advice session is soft deleted qap investor advice deleted triggered when an advice session is permanently deleted qap investor advice completed triggered when an advice session is completed qap investor advice report created triggered when an advice report is generated qap investor created triggered when a new investor is created qap investor updated triggered when an investor's information is updated qap investor soft deleted triggered when an investor is soft deleted qap investor deleted triggered when an investor is permanently deleted each event contains the following properties event id unique id for this specific event if an event triggers multiple webhooks, this will be equal across webhooks event type the type of the event (e g , "qap investor advice created" ) event object id the unique identifier of the affected object (e g , advice session id or investor id) event object owner id the unique identifier of the owner of the affected object (e g , advice investor id or owning advisor id) event owner id the unique identifier of the event’s owner this could be an advisor id or a client id event time the timestamp of the event in utc (e g , "2023 03 15t12 46z" ) event data a json object containing additional information about the event (e g , {} or {"investor type" "person","investor name" "john doe"} to ensure seamless integration with external systems, we provide a flexible configuration setup that allows you to define various aspects of the webhook request, such as http method, static authentication, custom headers, and an optional signing key for added security the resulting webhook request is tailored to your preferences for a post request, the event data is sent in the request body with a "content type" header set to "application/json" for a get request, the event data is sent as query parameters, excluding the event data object the webhook payload includes essential information such as the event type, object ids, owner ids, and event time if a signing key is provided, the "x quantfolio signature 256" header is added to ensure the authenticity and integrity of the webhook payload by leveraging quantfolio's webhook functionality, businesses can stay informed about important events on the platform and react accordingly in real time, improving efficiency and enhancing the overall experience for both advisors and investors