0:01 So a quick introduction to webhooks. We have those in the system for a while, but actually actively promoting those right now.
0:12 Maybe very quickly for those who don't know what this is for, but basically the API is a one way direction where you query Infigo about information.
0:25 So that means in case you want to understand about changes, you would have to consistently ask the API for changes and poll information.
0:36 And the webhook system will allow you to set up and configure endpoints where in figure will send out an event.
0:46 So basically you would be notified about those changes as they happen and basically you wouldn't have to poll, saving yourself some resources, us some resources, we have some customers who will actually use this quite extensively right now so they can certainly benefit from switching over to web hooks
1:06 for those status updates when items are being printed, shipped, orders completed, etc. For the sake of this demonstration, I will quickly set up one.
1:22 Obviously, I don't have an endpoint which could consume this. For that, I use a service called pipe dream, which I'll show you in a second, though, it's just visually possible to see this.
1:36 But when you go to Webhooks and Admin, we can set up a new one. And basically can give this a name.
1:48 And the main important thing for Webhook is that you specify an endpoint which we should call one when this comes in.
1:58 And Pipedream basically, this is a service which you can use to set up and do some of those migration tasks, but obviously you would use your application for it.
2:09 It just gives us an endpoint which we can call, so I can copy this into a clipboard and use this here.
2:21 And then I can specify different methods if it's a get or a post or some additional HTTP verbs can be used as well.
2:31 You can add some headers here for authentication or anything else in order you want to use this. And maybe it was important, you can change the mode, how those webhooks are being triggered.
2:43 The default one is delayed, which means whenever the change happens, it doesn't send the We're pulled out immediately, it batches them up, a background task process is that, that is just very good for us to save resources, and if it's not really time-critical, it wouldn't matter if there is a slight
3:04 delay in a few minutes. Delayed in batches will basically actually send out large batches, so if for large volume sites, where you have hundreds, if not thousand orders a day, And a lot of things move that makes a lot more sense because you will not get individual calls for each one But actually it batches
3:26 them up there. It will be some sort of CSV style data being sent to you where you have an information about All their elements which are being changed for the sake of the demonstration we do time critical which send them out Very quickly as soon as the event happens and then you can specify What is the
3:46 entity you want to be informed about an order, customer order line and product and changes and you can say what will be the events you would like status updates, cancel status deleted, created, updated or all of the above and basically that's when this webhook will be triggered and you can use multiple
4:07 webhooks for different things for different statuses or have them combined and then you can finally specify the data type and you see a sample of what this would look like and that you can use JSON, XML, etc.
4:21 and what is also very nice is for XML. You can use XSLT to transform this data to a format which your site understands.
4:30 you can test this XSLT transformation here to see what this will look like, but for now we will basically send just some standard XML for this purpose.
4:44 So let's save and create this this web hook and now theoretically as soon as something changes we should see this coming up here.
4:55 And because they've done an order line change, we could go into Shared Print Ops quickly and choose one of our jobs.
5:08 Michael, just quickly. Yalfeng is just asked and I won't get you on for this because it might be a short question answer, but if you've got anything else you want to add, you can jump on, but is this This is the webhook, the webhook page is already available to all of our customers on the call at the
5:24 moment. Yes, it is. It is available, right? So you should be able to find it in admin just by searching webhook for webhook.
5:32 So for example, if I change to the status here now, it will update here. And under the hood, the Infigo system will send out the webhook based on the configuration we've had here.
5:50 I took some time to see here now they came in there you go Chris thank you for filling that void thank you very much you can time critical is not immediate but it will send it out fairly quickly and then you see here all the events the status code which came back and you can see the original request
6:10 the transformed request in case I would have you see the response which came from pipe dream and the response headers and when we go in here, we also see them coming in now.
6:26 You can inspect them in a bit more detail. What is the data which has been transformed here and you see here our ID for example and the name of those changes.
6:44 And here as well, for example, in this instance, I just set it up that it stores the data of those changes and pings them in a request store, and that's basically how you can do this.
7:03 So, Mike, if our customers are going to want to fetch some information from Infigo, what are the sort of questions they need to ask themselves to determine whether they should do it via the API or via the web hooks as well?
7:16 Well, it's basically whenever you, or you want to look at a status update, that's where you should start using the web hook instead rather than polling.
7:27 Because obviously if you pull and you have a couple hundred active jobs there that is a couple hundred active API calls when you do one for the order and then several for the order lines potentially it adds up even more while this will get you an information whenever you need it based on on the change
7:47 . so it saves resources on your end, it saves resources on our end, and makes the integration much nice and smooth.
7:55 And when you think about larger scale platforms with many orders, doing it through polling is almost ridiculous, and the webhook is the way to go.
8:05 And they said it's very flexible in the way it can be set up, different events, different transformations on the data you can use get requests or post requests etc to really fill whatever you use to consume this you.