Closed maxl2287 closed 1 month ago
Why not just include this information in a proprietary header that the event dispatcher would understand? If the API consumer included a notificationAuthToken
, then that would have to be included in an additional header anyway so that the event dispatcher could construct the Authorization
header.
Problem description Currently, the expectation is that a QualityOnDemand service provider sends notifications directly from its service to a webhook using the notificationUrl provided in the request. However, if the provider forwards the event to another service for event dispatching, that intermediary service may not have access to the notificationUrl and therefore cannot fulfill the notification.
Possible evolution To address this scenario, we propose allowing the provider to include the notificationUrl within the data property of a CloudEvent. This approach ensures that essential information for notifications can be transmitted seamlessly, even when events are routed through intermediary services.