I think you mean 'orders/fulfilled' webhook, it triggers when your order get fulfillment status and send order data on your client in webhook body. You can use it as 'orders-fulfillment/create' (not an existing webhook)
Or u can use 'orders/update' or 'orders/create' webhooks, it is triggered when any order has been updated/created, regardless of the status of the order. Just check the order status inside the handlers of this webhooks, if you want to process only fulfillment orders.
Hope this helps you! 😉
Thanks for the feedback.
This is not what we're looking for.
We need to get the actual FulfillmentOrders data for the order and store in our database. We use this data to handle locations.
Now, we read all FulfillmentOrders on orders/updated but since this can happen tens of times more often than the actual updates of FulfillmentOrders it's using all the available GraphQL available query cost.
orders/fulfilled will only be triggered when the order is actually fulfilled? Because FulfillmentOrders are created on order creation, and changes can happen at any time without the order being fulfilled.
Maybe the best would be to use fulfillments/update webhook instead, and then read the FulfillmentOrders for this order? This one should happen a lot less times than orders/update.
The question then is if fulfillements/update happens every time a change is made to a FulfillmentOrder? For example if an item on the order is set to be fulfilled from another location.
Our dream would be to have a webhook that returns the data we need, and not based on another webhook topic, and then getting the data ourselves and use valuable resources.