RELATED IDEAS
RestApi Webhooks to subscribe to events
Please, fill in the below fields to enable the processing of your idea.
Who would benefit? |
Everyone building integrations |
What impact would it make? |
Extending the RestApi with responsive functionality |
How should it work? |
Using a series of RestApi endpoints one could: 1. Create new subscriptions 2. View existing subscriptions 3. View a list of events one can subscribe to 4. Delete subscriptions These subscriptions of course would contain a url that is called by inRiver when the relevant event occurs in inRiver. The url should be a POST method containing a payload of relevant data, whether it is a change to an entity, model, link, etc., etc.. |
Why is it needed? |
Currently if we want to know if something has changed, we need to build a traditional extension to listen to a relevant event, OR we have to poll RestApi. If we wish to build integrations by exclusively via RestApi, then there is no existing functionality to easily listen for events. |
Additional feedback, background or context: Building integration with external systems using Azure cloud and RestApi functions. Currently we need to have Channel, Entity and Link listeners and a Scheduled Extension to listen to events and send a custom event to Azure cloud.
