Hey there. I was hoping to get help with the Fulfillment resource question. Since 5/11/22 we started to notice an issue where Fulfillments returned via the Admin Rest API don’t have the notify_customer field in them anymore. We’re able to update the field via /update_tracking.json, but it’s not visible in any of the GETs.
1 Like
Not sure which API version is being used here, and in 2022-04+ the notify_customer field is only used for the POST requests. The field isn’t included in the example payload responses in the docs for GET requests to /fulfillments.json
Thanks for the reply! ?
Your documentation for all supported versions does include “notify_customer” field in the Fuflillment resource. I’m having a hard time understanding the rationale behind removing it from the GET responses, while still allowing its mutation.
What is your recommendation on viewing the current value of Fulfillment.notify_customer field?
Thanks for the reply! ?
Your documentation for all supported versions does include “notify_customer” field in the Fuflillment resource. I’m having a hard time understanding the rationale behind removing it from the GET responses, while still allowing its mutation.
What is your recommendation on viewing the current value of Fulfillment.notify_customer field?
1 Like
I have the same issue.
Does anyone know any other way to check value of Fulfillment.notify_customer?
Hi @lucnguyenfs ,
I would recommend using the orders’ events endpoint to check for a shipping confirmation email sent at the same time as the fulfillment as a workaround:
Hope that helps