Hi everyone,
I’m using the refunds/create webhook and filtering data with includeFields.
My payload includes refund_line_items[].line_item.fulfillment_status (following the REST schema), but the GraphQL Admin API marks LineItem.fulfillmentStatus as deprecated in favor of FulfillmentOrder.
Question: Is it safe to rely on fulfillment_status in webhook payloads for the foreseeable future? Since LineItem in GraphQL doesn’t seem to have a direct alternative like fulfillmentStatus (non-deprecated), I’m unsure if I should build logic around this field.
Thanks!
1 Like
Hey @Purushottam_Khedre, the GraphQL field is deprecated however the field does still appear in the refunds/create webhook payload so it is still supported in the context of this webhook. Before we recommend it though, can you share a little more context on your use case?
The reason I ask is we have made a lot of updates to these API’s over the years. Since you’re needing fulfillment status on a refund, some of our current return API’s and webhooks may be better suited.
Our documentation here covers the more current webhooks for fulfillment and order management apps as well as a guide on migrating from fulfillments:
Hey @Purushottam_Khedre, did the above help?